Community
Participate
Working Groups
Build Identifier: 20100218-1602 Our application uses the Properties View (Tree). Sometimes when an item in the view is clicked and this creates a (modal) dialog and then selection occurs on the dialog, items in the Properties View are also selected (possibly modified if they are elements as check-boxes or list-boxes). This seems to occur specially when a label (item in the tree), that generates the modal dialog, is double clicked fast and this somehow makes the resulting dialog behave not modal. This occurs on Mac OS X 10.5.8. The Eclipse version is 3.5.2 Cocoa (build ID 20100218-1602). Library versions used: - org.eclipse.core.commands_3.5.0.I20090525-2000.jar - org.eclipse.equinox.common_3.5.1.R35x_v20090807-1100.jar - org.eclipse.jface_3.5.2.M20100120-0800.jar - org.eclipse.osgi_3.5.2.R35x_v20100126.jar - org.eclipse.swt.cocoa.macosx_3.5.2.v3557f.jar Please note that this does not occur on Windows or Linux. See the attached application and the screencast which shows Reproducible: Sometimes Steps to Reproduce: 1. Expand a TreeItem. 2. Double click fast (this is important) on the "item xy" in the resulting subtree. 3. When the (Color) Dialog is created, first make sure you are on (choose) the Color Palettes tab. 4. Select labels (colors) on it. Even select below the last color in the palette, on the white space available there (as shown in the screencast). 5. Please note that selection on the Dialog causes selection in the tree behind; the Dialog does not behave as a modal. 6. If the described troublesome selection does not occur, please return to step 2 (maybe even restart the small application and return then to step 1) and make sure you double click fast on the "item xy".
Created attachment 174292 [details] Sample application to reproduce the issue
Please refer to http://drop.io/eclipse_bug_319857/asset/swt-bug-ontreeitem-mov for the screencast (sorry, it was to large to upload as an attachment).
This looks like a variant of bug 313208, which I am addressing for 3.6.1.
(In reply to comment #3) > This looks like a variant of bug 313208, which I am addressing for 3.6.1. Never mind -- this comment is irrelevant. I can't reproduce this on a fresh download of 3.6. Marking as fixed, but I can't give you the bug number or change that actually fixed it.