Bug 330143 - A patch to make RowLayout layout controls in reverse order on demand
Summary: A patch to make RowLayout layout controls in reverse order on demand
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-12 16:12 EST by Serge Yuschenko CLA
Modified: 2019-09-06 16:09 EDT (History)
2 users (show)

See Also:

Attachments
A patch for org.eclipse.swt.layout.RowLayout to layout controls in reverse order (881 bytes, patch)
2010-11-12 16:15 EST, Serge Yuschenko CLA 		no flags Details | Diff
View All 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 Serge Yuschenko CLA 2010-11-12 16:12:37 EST 
Build Identifier: M20100909-0800

With the addition of public variable reverse the org.eclipse.swt.layout.RowLayout can display controls in reverse order. This feature eliminates necessity to re-create the controls.

...
view = new Composite( parent, SWT.NONE );
rowLayout = new RowLayout( SWT.HORIZONTAL );
view.setLayout( rowLayout );
...

public void changeOrder() {
  rowLayout.reverse = !rowLayout.reverse;
  view.redraw();
}

Reproducible: Always
Comment 1 Serge Yuschenko CLA 2010-11-12 16:15:35 EST 
Created attachment 183044 [details]
A patch for org.eclipse.swt.layout.RowLayout to layout controls in reverse order
Comment 2 Carolyn MacLeod CLA 2010-11-15 09:54:18 EST 
Just curious - what is your use case for this? I am not sure that it is something that is generally useful.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:09:36 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.