Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 24398 - Java working set page allows empty working set
Summary: Java working set page allows empty working set
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 minor (vote)
Target Milestone: 2.1 M5   Edit
Assignee: Dani Megert CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-10-04 12:16 EDT by Knut Radloff CLA
Modified: 2003-01-29 16:33 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Knut Radloff CLA 2002-10-04 12:16:51 EDT
build 20021001

-create a Java working set
-expand a project containing more than one child
-select one child so that the project is gray checked
-close the edit dialog
-edit the working set
-uncheck the gray checked project
->No elements are checked but the finish button is enabled and no error message 
is displayed.

See also bug 24397
Comment 1 Dani Megert CLA 2002-10-07 13:20:33 EDT
The problem arises if the node has not yet been expanded
- need to check my code and platform code
Comment 2 Dani Megert CLA 2002-10-08 06:12:36 EDT
Fixed.
Available in builds >= I20021008
Comment 3 Knut Radloff CLA 2002-10-17 17:21:08 EDT
Verified fixed in build 20021016
Comment 4 Knut Radloff CLA 2003-01-28 16:34:31 EST
This is not completely fixed:
In a structure 
Project1
  folder1
    file1

-Create a working set and select file1.
->Project1 and folder1 are gray checked
-Collapse folder1
-Uncheck Project1
->No items are checked yet the finish button is still enabled. If you close the 
edit dialog and reopen you will get an error message indicating that no items 
are checked.

I fixed this for the ResourceWorkingSetPage. See bug 24397.
Comment 5 Dani Megert CLA 2003-01-29 05:58:12 EST
The current implementation is due to performance problems when clicking  in the
UI (it took almost a minute with very large workspaces in slow machines).

Your fix will surface those problems again.

I have fixed the problem you report here by changing the validation mechanism
(see JavaWorkingSetPage.validateInput in JDT UI HEAD.

Comment 6 Knut Radloff CLA 2003-01-29 16:33:27 EST
Performance could only be a problem when a large number of items are checked or 
gray checked because I now recursively uncheck children when an item is 
unchecked. I tried this with all children of org.eclipse.ui.workbench and 
performance is not a problem. Perhaps this would be different when working with 
Java elements.
There was a different problem with my fix which I corrected. Your fix is nice 
because it's simple. However, I'll keep mine for the time being unless it 
causes problems.