| 2008-10-10 12:03:09 |
Jamie Bennett |
bug |
|
|
added bug |
| 2008-10-10 15:00:16 |
Matt Layman |
entertainer: status |
New |
Triaged |
|
| 2008-10-10 15:00:16 |
Matt Layman |
entertainer: importance |
Undecided |
Medium |
|
| 2008-10-10 15:00:16 |
Matt Layman |
entertainer: statusexplanation |
|
I've seen this too. However, I disagree about this working earlier. I don't think that the ScrollMenu widget has ever had the concept of memory. I would think that the ScreenHistory would ensure that position is preserved, but maybe that's not the case. |
|
| 2008-10-12 19:18:00 |
Joshua Scotton |
entertainer: assignee |
|
joshuascotton |
|
| 2008-10-12 19:18:00 |
Joshua Scotton |
entertainer: statusexplanation |
I've seen this too. However, I disagree about this working earlier. I don't think that the ScrollMenu widget has ever had the concept of memory. I would think that the ScreenHistory would ensure that position is preserved, but maybe that's not the case. |
In line 549 of user_interface, which is part of the handling code for backspace, the update() method of the screen is called.
For main_screen.py this is:
self.group.remove(self.menu)
self.create_main_menu()
Hence all sense of position is lost.
I'm going to take a look at making this have some "memory"... ;) |
|
| 2008-10-13 19:12:02 |
Joshua Scotton |
entertainer: status |
Triaged |
Fix Committed |
|
| 2008-10-13 19:12:02 |
Joshua Scotton |
entertainer: statusexplanation |
In line 549 of user_interface, which is part of the handling code for backspace, the update() method of the screen is called.
For main_screen.py this is:
self.group.remove(self.menu)
self.create_main_menu()
Hence all sense of position is lost.
I'm going to take a look at making this have some "memory"... ;) |
|
|
| 2008-10-30 10:38:17 |
Paul Hummer |
entertainer: status |
Fix Committed |
Fix Released |
|
