Community
Participate
Working Groups
Build Identifier: 20100617-1415 On Mac clicking on a checkbox in a CheckboxTreeViewer causes the corresponding row to be selected. This does not happen on Windows. Also I could not find an Apple style guide that would require it to be like that. I think the behavior should be the same in this case. P.s. I was not sure about the product and component and copied them form another bug related to the CheckboxTreeViewer. Reproducible: Always Steps to Reproduce: 1. Select an element in a CheckboxTreeViewer. 2. Click on the checkbox in a different row. 3. The selection changes.
Prakash, could you please test this on your machine and confirm the bug ? Thanks!!
Tried SWT Snippet# 274 and checking does selects the the entire row. Moving the bug to SWT. Also shouldn't it select/deselect when the space bar is pressed?
(In reply to comment #2) > Also shouldn't it select/deselect when the space bar is pressed? Only if "Full Keyboard Access" is turned on. (System Preferences -> Keyboard -> Keyboard Shortcuts)
Clicking the triangle to expand or collapse a parent element does not have this effect. There seems to be a "save zone" for that. Maybe it could just be extended to contain the check box as well.
I seem to recall fixing this at one point. It may be that I did it for Table and not Tree.
Scott -- I would be very appreciative of and willing to test a patch for this bug. Thanks, Steve.
Created attachment 183182 [details] Fix I had worked on this at one point, and fortunately saved my work. There was one last problem to iron out; it's all working now.
(In reply to comment #6) > Scott -- I would be very appreciative of and willing to test a patch for this > bug. Thanks, Steve. If you know how to build the SWT, go ahead. I'll check it in Tuesday AM.
Fixed > 20101116.
.
Great. It works for me too. Thanks for the fix.
Scott -- Is it possible to also commit this fix to the 3.6.x branch? We are planning to releasing an RCP app based on 3.6.2. Unfortunately, I am unable to wait to the release of 3.7.0.
I have cloned the bug for 3.6.2. We don't have a 3.6.2 plan just yet; I'll see what I can do.