Community
Participate
Working Groups
3.6 RC2. While going through the 3.6 N&N items I tested the new Java breakpoint details: when doing this I changed some values but they were not respected. It is not obvious that a view is dirty and even after leaving the view I do not get any feedback. Users are not used to see/have dirty views.
In addition: the current state is not filled into the properties dialog.
OOPS: and when switching between breakpoint my current dirty changes are discarded but the view stays dirty :-(.
The "auto-save" policy is to save changes when the input to the detail pane is changed. Thus, losing focus does not auto-save changes. However, selecting another breakpoint will save changes (or closing the breakpoints view, or putting another view on top of the breakpoints view...). It might be better to "auto-save" when focus is lost as well.
(In reply to comment #2) > OOPS: and when switching between breakpoint my current dirty changes are > discarded but the view stays dirty :-(. Look like this happens when the data is invalid - for example characters in a hit count value.
>Look like this happens when the data is invalid Indeed. And once in that state the dirty mark (*) never goes away until I make some other changes. If the code can handle invalid values being stored, then the simplest thing would be to just store that invalid string. >It might be better to "auto-save" when focus is lost as well. For text widgets it has to do it on focus lost and dispose/close of the view (including shutdown).
*** Bug 399298 has been marked as a duplicate of this bug. ***
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. -- The automated Eclipse Genie.
