| Summary: | [Preferences] PreferenceDialog performOK() does not restore OK button if save fails | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | icemank |
| Component: | UI | Assignee: | Platform UI Triaged <platform-ui-triaged> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | minor | ||
| Priority: | P5 | CC: | remy.suen |
| Version: | 3.0.1 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | stalebug | ||
|
Description
icemank
Update: now the performOK() functions as it should. However, there is still a problem- if performOK() returns false, the OK processing aborts correctly- however it leave the OK button disabled. The OK button can be re-enabled only by switching to another preference page and then back again. My workaround is to manually re-enable the OK button in my performOK() method before returning false. The question is what to do here. If the save fails do we remove that page from the list of pages to save? And do we need to keep track of the ones we already called performOK on to make sure we don't do things twice. There are a few subtleies with this issue which could break people. (In reply to comment #1) > However, there is still a problem- if performOK() returns false, the OK > processing aborts correctly- however it leave the OK button disabled. This should've been fixed by the changes for bug 123965. 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. |