Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 322279 - [Tree] CheckedStateListeners broken for new tree
Summary: [Tree] CheckedStateListeners broken for new tree
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.4   Edit
Hardware: All All
: P3 blocker (vote)
Target Milestone: 1.4 M2   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-10 15:34 EDT by Cole Markham CLA
Modified: 2010-09-08 09:18 EDT (History)
2 users (show)

See Also:

Attachments
Patch to fix the problem temporarily. (1.12 KB, patch)
2010-08-10 15:40 EDT, Austin Riddle CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Cole Markham CLA 2010-08-10 15:34:53 EDT 
Checked state is not being propagated from the client to the server using the new tree from CVS head.
Comment 1 Austin Riddle CLA 2010-08-10 15:40:45 EDT 
Created attachment 176273 [details]
Patch to fix the problem temporarily.

The TreeItemLCA does not seem to be receiving checked events.

I couldn't quite figure out where the most appropriate place to propagate the event back to the LCA is. We needed this fixed today so here is a patch to add a hack that sends the event back from setChecked().

I am sure this is not the correct way or place, but we couldn't figure out how the update event scheme was intended to work.
Comment 2 Ivan Furnadjiev CLA 2010-08-11 08:49:47 EDT 
Fixed in CVS HEAD.
Comment 3 Tűz Csaba CLA 2010-09-08 08:07:49 EDT 
(In reply to comment #2)
> Fixed in CVS HEAD.

We got Eclipse RAP Tooling yesterday from repository, that's 08.11 15:?? build, but we still have this issue.
As I could figured out, SelectionEvent doesn't occurs on JS checkbox state change.
I suggest reopen
Comment 4 Ivan Furnadjiev CLA 2010-09-08 08:18:09 EDT 
Yes... it's possible to have this problem with 1.4M1 if you use "standard" "Client-side Library Variant" (check your launch configuration). The problem does not exist with 1.4M1 and "debug" variant. With CVS HEAD (and upcoming 1.4M2) this works in both library variants.
Comment 5 Ivan Furnadjiev CLA 2010-09-08 09:18:22 EDT 
I will change the target milestone to 1.4M2 to avoid such situations.