Summary: | DoubleClickEvent only fired in first column of TableViewer | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Pierre-Yves Bigourdan <pyvesdev> |
Component: | UI | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | mistria, paul-eclipse |
Version: | 4.13 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows All | ||
See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=553376 | ||
Whiteboard: |
Description
Pierre-Yves Bigourdan
2019-10-29 17:37:35 EDT
@Mickael, added you to CC list so that you're aware this is causing issues with lsp4e on Windows. Thanks Pierre-Yves, I wasn't aware of this. On LSP4E side, we could rework a bit the list to use a CheckboxCellEditor instead of double-clicking. This might be more consistent with other parts or UI and hopefully make things usable on Windows by avoiding that bug. Hmmm... I've been playing around with TableViewer objects, and apparently creating them with SWT.FULL_SELECTION seems to solve the problem on Windows (new TableViewer(composite, SWT.FULL_SELECTION)). Any ideas why this flag is required for this operating system? (In reply to Pierre-Yves B. from comment #3) > Hmmm... I've been playing around with TableViewer objects, and apparently > creating them with SWT.FULL_SELECTION seems to solve the problem on Windows > (new TableViewer(composite, SWT.FULL_SELECTION)). Any ideas why this flag is > required for this operating system? This seem to be intentional Windows behaviour. Recognized the same when I made my fake control example in bug 550555 comment 5. The relevant code is in SWT Table#sendMouseDownEvent where the hit test only check for the first column if not in FULL_SELECTION mode. Quite a few other bugs seem to mention similar behaviours, for instance Bug 396604. If it really is intentional behaviour, maybe it's worth updating some of the Javadocs to avoid users being caught off-guard in the future? |