Community
Participate
Working Groups
Test Case: 1. Create a new plugin project. 2. Use "Plug-in with a view" template to create a plugin with the Sample View. 3. I modified the SampleView to include a combo box cell editor and cell modifier. (I will attach my test plugin.) Steps to reproduce: 1. Activate the cell editor in the Sample View 2. Then, quickly click on the drop down from the combo box. Results: The combo box loses focus quickly before allowing the user to set a selection. The cell modifier is told to modify values. If I wait a little bit for the cell editor to finish its activation, then the drop down menu stays as expected when I click on the drop down button.
Created attachment 65392 [details] test plugin
Is this still an issue? I tried our test project (thanks!) and couldn't get it to happen (maybe I'm just too slow).
i have meet this problem too, i'm expecting that be resovled as soon as possible.
Sorry but I can't get this to happen on my machine...what builds did you folks see the problems in ?
I see the problems in Eclipse SDK,Version: 3.3.1,Build id: M20070921-1145.
Hmmm, could you try this out in 3.4M4? Note that issues of this type are unlikely to make it onto the 3.3.2 'fix list', the focus of the point fixes is to address major issues only (the primary concern is maintaining the stability of the 3.3 stream).
i have find what induce this problem. i used CCombo.java is of old version. setFocus in 3.3 is follow public boolean setFocus () { checkWidget(); if (isFocusControl ()) return true; return text.setFocus (); } my used old version hasn't the sentence if (isFocusControl ()) return true; i want to know when this sentence was added.
If you want to know when the code was added to CCombo, check it out and use the 'Show History' command. This will give you a change log of all changes to the file (including dates).
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.
