Say we have a combobox element in TOOLS -> OPTIONS.
Right now we need to single click on the combobox to give it focus, then single
click on it a second time to get it to display all possible values. I strongly
believe we can remove the need for the first click.
We should modify the UI across all of Netbeans such that any item having the
mouse over it gains "virtual focus" which is NOT equivilent to real focus..
Basically put, if I am in Combobox A and I move the mouse over Combobox B,
combobox B will look/feel like I have focus on it (ie: I can single-click to
get a list of options) but hereby lies the difference between "virtual focus"
and actual focus. In the case of a real focus change, when I move from combobox
A to combobox B, I save my settings for combobox A (because I left it), but in
the case of "virtual focus", combobox A doesn't save it settings or lose
its "real focus" until after I click on combobox A.
If you need any more clarification on what I mean, please ask. I think this
change will make Netbeans much more intuitive and productive to use.
Target milestone -> 3.3.1.
Target milestone -> 3.4
I believe this is more a bug either in property sheet itself or in
focus transferring. Single click on combo works ok in regular
situations, and it should work here as well. David, please provide
further evaluation, thanks.
PropertySheet (PropertyPanel/SheetButton more precisely) works this way:
1. It is in so called read state
2. first click --> goes to so called write state
if the write state is combo --> show the combo, but collapsed
3. second click --> expand the combo
We might want to avoid the first click. I am not sure we want it.
Maybe the "plastic" option might by used to indicate this.
But anyway - this is clearly property sheet request for enhancement.
It seems reasonable to me, and probably easily implementable.
UI team, what do you think and what is common behaviour of combo boxes
in property sheets in other IDE products?
For me the effort required is not adequate to the expected benefit of
this so I postponed it in future. It would nice to have in future if
time/resources would allow.
*** Issue 20468 has been marked as a duplicate of this issue. ***
*** Issue 20642 has been marked as a duplicate of this issue. ***
Property sheet issue, as i know Tim is working on this.
Tim, it is available in the new implementation of Property Sheet,
isn't it ?
This works in the new property sheet implementation, so it will
work in Options, which uses a PropertySheet.
PropertyPanel (for example, the thing that you click to edit
editor colorings) will eventually be converted to use the
new property sheet rendering infrastructure, which will
take care of the rest of the two-clicks-to-drop-down
Adding dependency on property sheet rewrite umbrella issue.
Fixed - new property sheet committed.
verified in [nb_dev](20030718)