Bug 170201 - And possibility to use percentage values for height and width for GridLayout/RowLayout
Summary: And possibility to use percentage values for height and width for GridLayout/...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Veronika Irvine CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-11 06:08 EST by Thomas Schindl CLA
Modified: 2019-09-06 16:14 EDT (History)
1 user (show)

See Also:

Attachments
Example Patch for RowLayout/RowData (6.72 KB, patch)
2007-01-11 07:09 EST, Thomas Schindl CLA 		no flags Details | Diff
A better one including a snippet to give it a try (9.71 KB, patch)
2007-01-11 09:11 EST, Thomas Schindl CLA 		no flags Details | Diff
Show Obsolete (1) 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 Thomas Schindl CLA 2007-01-11 06:08:14 EST 
I know that I can use FormLayout to use percentage values but Grid-Layout is flexible enough for most cases and it would be a nice thing if one could set the width/height of a "grid-cell" using percentage values instead of absolute values.
Comment 1 Thomas Schindl CLA 2007-01-11 07:09:58 EST 
Created attachment 56758 [details]
Example Patch for RowLayout/RowData
Comment 2 Thomas Schindl CLA 2007-01-11 08:10:51 EST 
Comment on attachment 56758 [details]
Example Patch for RowLayout/RowData

this is not really working I think I need to rethink it
Comment 3 Thomas Schindl CLA 2007-01-11 09:11:06 EST 
Created attachment 56761 [details]
A better one including a snippet to give it a try
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:14:50 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.