Bug 237346 - SashForm doesn't provide a option for controlling the divider
Summary: SashForm doesn't provide a option for controlling the divider
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.4   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Silenio Quarti CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-16 16:00 EDT by Mike Schrag CLA
Modified: 2019-09-06 16:04 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Schrag CLA 2008-06-16 16:00:45 EDT
On OS X (and I assume others) there are actually two flavors of split pane -- one with a thin divider, and one with a thick divider (that has a grab handle). You can see both in Mail.app on Leopard, the vertical divider is a thin and the horizontal divider is the thick.  Currently SashForm only appears to expose the thin divider variant.  It would be nice to have an SWT.THICK or similar hint that can be passed to the Sash to specify that we want to have the variant with the handle.
Comment 1 Steve Northover CLA 2008-06-17 09:35:51 EDT
Perhaps we could draw the handle when the width or height is thick enough to see it?
Comment 2 Mike Schrag CLA 2008-06-17 09:48:35 EDT
Two things on this -- First, I think there's an OS-specific thickness for the variant with a handle, and this probably differs between OS's (so getting proper cross-platform impls might be tricky) and the second is that I would be nervous about trampling on someone's custom rendering based on the existing behavior.  That is, if you have an SWT app already that is drawing a handle yourself, we would trample on that with this change.  I'll take a look at GTK and Windows and see is there is any analogue to this concept that might better justify a new setting.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:04:27 EDT
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.