Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 340406 - DynamicToolBarContributionItem class need to proxy computeWidth()
Summary: DynamicToolBarContributionItem class need to proxy computeWidth()
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-18 05:54 EDT by Prakash Rangaraj CLA
Modified: 2019-11-27 06:58 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Prakash Rangaraj CLA 2011-03-18 05:54:14 EDT

    
Comment 1 Prakash Rangaraj CLA 2011-03-18 05:55:26 EDT
computeWidth() is a protected method. Either we need to (*) create a new API or (*) use reflection
Comment 2 Miles Parker CLA 2011-04-14 14:40:40 EDT
Can you suggest a workaround or has there been recent progress on this? As it is, I can't control the widget width in my toolbar under 3.7 at all unless I contribute it programmatically. (It was quite difficult diagnosing what wasn't working here -- I was convinced I must have been doing something wrong!)

thanks,

Miles
Comment 3 Prakash Rangaraj CLA 2011-04-15 00:02:13 EDT
This one won't be fixed for 3.7, you have to resort to contribute programmatically.
Comment 4 Miles Parker CLA 2011-04-15 00:19:13 EDT
Thanks Prakash. Just to be clear, this means that there is no way to use control contributors for controls like Text that need to set their own size? (Aside from manually adding them through advisors, which doesn't work well for me because I can't get the ordering I need.)

BTW, I sent you a note about the Mac toolbar work, cool stuff.
Comment 5 Lars Vogel CLA 2019-11-27 06:58:12 EST
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.

If the bug is still relevant, please remove the stalebug whiteboard tag.