Lunar Ocean Y’a pas anguille sous roche, mais probablement baleine sous gravillon…

Dear committer, prepare your jFace-foo !

We have a case where we have a CheckBoxTreeViewer that represents a list of elements.

The list in itself is informative. The user is going to be very interested into what is selected, and what isn’t.

It’s certain that at some point he will expand the tree to look at some nodes, come back, etc.

Right now, you cannot disable the checkboxes of a CheckBoxTreeViewer without disabling the whole tree.
So that means that your users cannot check checkboxes (that was the intent), but they also cannot expand the tree.

What if you’d like to disable some checkboxes only ? That’s unsupported too.

Unfortunately, there is no solution for this problem so far. I filed 259092 earlier today to investigate the issue, and it seems you can try to add a listener to revert the check event when the user clicks on checkboxes. Users would still see the items as enabled though, and given the complexity of the interface, adding a tooltip, a new decoration is just going to be confusing.

If you have a spare vote to cast for this bug, a comment, and idea, and ideally a patch, let’s talk about it on the bug!

Somehow I had the feeling that I was in control when it came to specifying the browser I wanted to open.

Apparently, it’s true for external browsers. For internal browsers, ie those that show in a view or an editor in Eclipse, not so much.

What happens is that the information get lost. You specify the browser type when you do the call to open the browser:

PlatformUI.getWorkbench().getBrowserSupport().createBrowser(SWT.MOZILLA, ...);

But this is simply ignored by the internal editor. Not for too long though, since I attached a patch to 259171 fixes the problem.

Your feedback on this is welcome, of course please feel free to comment on the bug rather than here.