| Summary: | [formatter] Formatter profiles store even though I clicked 'Cancel' | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Dani Megert <daniel_megert> |
| Component: | UI | Assignee: | Martin Aeschlimann <martinae> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | dirk_baeumer, hudsonr |
| Version: | 3.1 | ||
| Target Milestone: | 3.2 M3 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Dani Megert
Martin, can you please investigate in a fix for 3.1.1. By design all changes to profiles (add/remove/edits) are directly applied in the profile store. The only setting in the preference store is the profile selection; it in fact could be reverted on cancel. Problem with that is that it then might point to a non-existing profile or a profile that is completly different than before. So we always directly apply the profile selection on every change. Cancel has no meaning. I would leave the current behaviour also for 3.2. 'Cancel' is not so important here as it takes just one click to specify the previous profile. I see the problem, but I don't see an easy solution. Reopen if you don't agree. The behavior can really be surprising and it contradicts to other preferences UIs, e.g. look at the code template preferences: you can edit a template, press OK on the edit dialog, then press Cancel on the preference page ==> changes are not applied to the template. Yes, I can revert it once I've realized that 'Cancel' did not work but I might already have formatted several files and even committed them. It is not a 3.1.1 candidate for me (unless the fix would be trivial, however for 3.2 this should be improved. For me an acceptable fix would be: - do not immediately store when I switch templates (disable OK if it has been deleted, and display 'deleted'. Maybe the removal can even be postponed until 'OK' is pressed?) - make it clear to the user that editing a profile leaves the preferences sandbox and all changes are immediately saved . not for 3.1.1 *** Bug 110990 has been marked as a duplicate of this bug. *** fixed > 20051006 Verified using I20051031-2000 Marking as verified. |