Bug 197237

Summary:	[SashForm] SashForm items exact size
Product:	[Eclipse Project] Platform	Reporter:	Mohsen Saboorian <mohsens>
Component:	SWT	Assignee:	Duong Nguyen <duongn>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	Brian.Miller, lafeuil, steve_northover
Version:	3.3
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Mohsen Saboorian

2007-07-20 00:32:50 EDT

The current API for handling SashForm gives you just a proportional array of integer weights for children. Also there is no (direct) way to set exact width of a child of SashForm.
I wanted to ask to also add support for a method like SashForm.setChildSize(int childNo, int width), in order to set width/height of a sash form child exactly.
This can be helpful for example in a case that you have a pane separated from the main body of you app, with a Sash. When user maximizes the shell, pane is also resized which is not very good, because pane size should remain unchanged.

I hope I am clear :)
Thanks.

Comment 1 Brian Miller

2008-03-24 15:02:39 EDT

SashForm is a disaster.

Comment 2 Steve Northover

2008-03-24 17:26:38 EDT

I can think of more serious disasters than this!  If SashForm doesn't cut it for you, you can implement your own behavior using Sash.  See http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/org.eclipse.swt.snippets/src/org/eclipse/swt/snippets/Snippet107.java

Comment 3 Mohsen Saboorian

2008-03-25 01:04:00 EDT

I know the snippet, so I just filled a feature request. I believe that this is a must for the current SashForm API. Sash is too complex. Adding Listener, and newing a number of FormAttachments are already disasters ;).

Comment 4 Steve Northover

2008-03-25 10:35:05 EDT

code == disaster

Comment 5 Eclipse Webmaster

2019-09-06 16:08:37 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.