Community
Participate
Working Groups
1. Select a project with folders in the Navigator 2. From the menubar select File > Export... 3. In the export wizard, select File System, then click Next 4. Expand the selected project in the wizard and click on a folder containing multiple files 5. All checkboxes from the project to the folder to the files should be checked with a white background, indicating that there are no partial selections 6. Uncheck one file, the project and folder checkbox backgrounds change to gray as expected to indicate a partial selection 7. Recheck the checkbox unchecked in step 6. Error -> The project and the folder checkbox backgrounds remain gray instead of returning to white.
Deferring to 2.2.
Defering. Please re-open this bug if you feel it is important for R3.0.
Still an issue in 3.1 (build I20050509).
Same problem when unchecking/rechecking a subfolder instead of a file.
Using 3.1 GA, when I multiple-select some projects and folders in the Package Explorer View (in "Show Working Sets" mode) and chose "Export" - "File System", the selection is *completely lost* and nothing is selected for export in the wizard.
(In reply to comment #5) > Using 3.1 GA, when I multiple-select some projects and folders in the Package > Explorer View (in "Show Working Sets" mode) and chose "Export" - "File System", > the selection is *completely lost* and nothing is selected for export in the wizard. Sorry, that seems to be a different bug, I filed it against JDT as bug#102485
Re-tested with R3.3 and we still have the problem. SWT is going to add a snippet to show the correct way to maintain the check state in the Tree. I will append a link to it here once they add it.
Here is a link to the SWT snippet to show how to update the checkmarks properly: http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet274.java
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
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.
Have checked with 4.12.0 Still it is existing. Needed to fix it.
