Community
Participate
Working Groups
3.3M5 It is not possible for a derived MultiPageEditorPart to reject a page change, possibly because the old page was dirty, and the user responded no to a save dialog. (The page change actually occurs as soon as the dialog box is shown and long before it is answered.) The problem is that the application page state is maintained in the GUI not by the application, so the change occurs instantly. It is not even possible for pageChange to determine what the previous page was, unless the derived class has its own cache. Requires an activePageIndex field that is maintained by pageChange, and interrogated by getActivePage().
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
Surely cannot be CLOSED until a relevant committer triages?
