Bug 130801 - [Contributions] Add setMenuText() to MenManager
Summary: [Contributions] Add setMenuText() to MenManager
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: All Windows XP
: P5 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-03-07 15:37 EST by tejashshah3 CLA
Modified: 2019-09-06 16:09 EDT (History)
1 user (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 tejashshah3 CLA 2006-03-07 15:37:33 EST 
When I create menu's dynamically, I need to change the Main Menu Title, on the menu bar, based on what the user.  The MenuManager does not allow the text to be updated.  I can get the MenuItem and update the text but when window loses focus, the Menu Title is reset to the value from 'getMenuText()' in MenuManager, not the MenuItem.  

I have currently extened MenuManager and added a setMenuText() to get around this issue.  Does it make sense to add setMenuText() to MenuManager itself?
Comment 1 Michael Van Meekeren CLA 2006-04-21 13:56:15 EDT 
Moving Dougs bugs
Comment 2 Paul Webster CLA 2007-04-05 19:05:00 EDT 
Assigning to component owner
PW
Comment 3 Remy Suen CLA 2007-07-01 22:21:29 EDT 
(In reply to comment #0)
> I have currently extened MenuManager and added a setMenuText() to get around
> this issue.  Does it make sense to add setMenuText() to MenuManager itself?

Maybe you can attach a patch? Did you override getMenuText() also? It seems like the menuText field is private, so I'm not sure how you're assigning the String value from your setMenuText method over to it.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:09:57 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.