Bug 25960 - Status bar contributions of different sizes
Summary: Status bar contributions of different sizes
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 2.1   Edit
Hardware: PC All
: P5 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-11-10 21:40 EST by Sebastian Davids CLA
Modified: 2019-09-06 15:31 EDT (History)
0 users

See Also:

Attachments
status fields can be of different sizes (3.55 KB, patch)
2002-11-10 21:44 EST, Sebastian Davids CLA 		no flags Details | Diff
status fields can be of different sizes (3.55 KB, patch)
2002-11-10 21:48 EST, Sebastian Davids 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 Sebastian Davids CLA 2002-11-10 21:40:46 EST 
Right now, the status bar contributions on the right size are all equal size.

Their sizes should be adjustable, so that one field can be larger (smaller) than
the other two.
Comment 1 Sebastian Davids CLA 2002-11-10 21:44:36 EST 
Created attachment 2364 [details]
status fields can be of different sizes
Comment 2 Sebastian Davids CLA 2002-11-10 21:48:04 EST 
Created attachment 2365 [details]
status fields can be of different sizes

the patch above already incorporated changes for bug 25961

in this patch all 3 status fields have the same size = 9 characters
Comment 3 Sebastian Davids CLA 2002-11-10 21:48:55 EST 
see bug 25961 for one reason why this feature is useful
Comment 4 Kai-Uwe Maetzel CLA 2003-06-16 04:03:42 EDT 
See bug 25961 for comment. Moving to later.
Comment 5 Dani Megert CLA 2007-06-22 09:59:14 EDT 
Get rid of deprecated state.
Comment 6 Eclipse Webmaster CLA 2019-09-06 15:31:46 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.