Community
Participate
Working Groups
I have a tablet PC and I am occasionally use it with eclipse while on the go. One things that turned out to be very tedious, is that some eclipse views, notably those that use a tree view (e.g. Navigator, Package Explorer, ...) do not allow to select multiple items using a "rubber band selection", i.e. selecting multiple items by drawing a frame around them (like e.g. the Windows Explorer allows). Selecting multiple items using Shift and Control keys is extremely complicated and almost unusable with a pen only. I recently wanted to reorganize a project and the lacking possibility to select more than a single file at a time made me give up (or rather delay it until I was back at my desktop with mouse and a full keyboard)... Is there a way to enable rubber band selections in eclipse (or maybe SWT)? It would be really cool, if eclipse could provide such an option! Or some alternative mean that allows to conveniently select multiple items in a list or tree view, e.g. like the leading tiny checkboxes that Vista's Explorer offers (under Tools => Folder Options => Views => "use checkboxes to select items"). These are absolutely ideal for pen only operation! Cheers, Michael
Marquis selection is supported for the table provided that mouseDown isn't hooked. It is not currently supported for trees.
This is already working when mouse down is not hooked on a table. It is not working for trees. Felipe is investigating marquis style block selection for StyledText so a version of his code could be used for tree. In any case, Eclipse will need to stop listening for mouse down in tables to enable the code. I believe that, since Eclipse does not use the selection event in a standard way (the selection policy code I no longer remember why it was needed), I think we are blocked. JFace can't remove the code so the feature won't be enabled.
... but this would be a cool native feature to enable in Eclipse somehow for table and implement for tree.
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.
