Community
Participate
Working Groups
Build ID: I20070625-1500 Steps To Reproduce: creating a preference panel with BooleanFieldEditor doesn't allow to control their checked state. More information: Workaround: 1. I created a class inheriting from BooleanFieldEditor to acces some protected methods : getChangeControl() and doLoad() 2. I used getChangeControl().setSelection but the wasSelected internal state is not maintained. 3. Calling doLoad reset the wasSelected value.
FieldEditors generally do not allow programmatic setting of their values. They obtain their value from the preference store supplied when they are created, and set the preference value if the user changes it. Some field editors provide convenience methods for getting the current value, but none provide programmatic changing of the value. To consider deviating from this design, I would need to better understand what you are trying to accomplish.
I have 3 preferences : 1 generate info 2 check info 3 validate info When 1 is unchecked 2 & 3 have to be unchecked and disabled when checking 1, 2 has to be enabled When 2 is checked 3 has to be enabled. The problem is that using getChangeControl().setValue(true) on 2 will not reset its wasSelected value. Then when clicking on button 2 no selection event is triggered because the wasSelected didn't change. I understand that using protected method like getChangeControl() and doLoad() is clearly overpassing the design you created but I still need to workaround the limitation of non being able to programtically interact with the FieldEditor.
as per 2009 triage guidelines
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.
