Community
Participate
Working Groups
preamble: Testing CoolBar first on win32 and gtk, it seems that DragDetect is fired whenever a CoolItem is dragged, but it is NOT fired if a drag is initiated on a part of a CoolBar that is not a gripper. I'm therefore assuming that the intent of DragDetect for CoolBars is to notify listeners precisely whenever a CoolItem drag begins. steps for motif: - run the ControlExample, select the CoolBar tab - listen for DragDetect - drag a CoolItem within the example CoolBar and note that no DragDetect is fired, so this is inconsistent with the behaviour that I assumed to be correct above and hence with the other platforms - however, try to drag a CoolItem in the example CoolBar by using the correct motif drag trigger (either middle mouse button or a mouse chord) and note that DragDetect IS fired in this case, but the CoolItem will not become draggable since this isn't the trigger that the control wants - so the platform trigger for DragDetect is being respected here, but in this case it doesn't match the semantics of the emulated widget, which uses button 1 for dragging
DragDetect is intended to indicate that drag & drop operation should start, not that a cool item has been dragged. However, there seems to be a platform difference.
If the meaning of DragDetect is no different for CoolBar than for other widgets, then this is working correctly. It's unfortunate that the trigger for dragging a CoolItem matches the usual drag trigger on some platforms but not on others (ie.- motif), because as a result there are probably clients that are hooking drag detect with the assumption that it behaves like the preamble from comment 0, and are failing on motif as a result of this not being true.
There is a platform difference that still needs to be addressed.
Grant to prioritize.
Work is discontinued on SWT's Motif port.
Closing report, platform is discontinued.
