Bug 318080 - Allow StackLayout#computeSize() to only use the visible control report the size
Summary: Allow StackLayout#computeSize() to only use the visible control report the size
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-26 10:44 EDT by Thomas Schindl CLA
Modified: 2019-09-06 16:04 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Schindl CLA 2010-06-26 10:44:09 EDT 
I have a Composite which is the child of a ScrolledComposite and when the topControl changes I recalculate the size needed by the Composite and update the minSize of the ScrolledComposite.

The problem is that when using computeSize() the StackLayout uses the size of ALL its children instead of only the current topControl.

I've subclassed the layout but thought it be maybe possible to directly provide this feature as part of the StackLayout.

The code I use can be obtained from here: http://dev.eclipse.org/viewcvs/index.cgi/e4/org.eclipse.e4.tools/bundles/org.eclipse.e4.tools.emf.ui/src/org/eclipse/e4/tools/emf/ui/common/EStackLayout.java?view=markup
Comment 1 Remy Suen CLA 2010-06-26 13:50:52 EDT 
This feels kind of like bug 278572. Or is this something different?
Comment 2 Thomas Schindl CLA 2010-06-26 14:09:10 EDT 
... well this talks about layout() I'm talking about computeSize() which takes all children into account which might be a good thing under certain cirtumstance but has undesired effects in my use case where I need to calculate the min-size for the ScrolledComposite to show Scrollbars.
Comment 3 Scott Kovatch CLA 2010-07-14 20:21:04 EDT 
Doing some housekeeping -- I don't think this is Mac-specific, so moving to All/All.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:04:16 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.