Bug 306320 - Need notification for creation of MenuItem
Summary: Need notification for creation of MenuItem
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 242357
  Show dependency tree
 
Reported: 2010-03-18 02:24 EDT by Prakash Rangaraj CLA
Modified: 2019-09-06 15:34 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 Prakash Rangaraj CLA 2010-03-18 02:24:50 EDT 
We have reference to a Menu. We need to know when a client creates new MenuItem in that menu. Currently I don't see any way to get notified of the creation of the menu items. I tried SWT.Skin, but didn't get any notification. It would be great if we could get a notification when a MenuItem is created on a Menu. 

Encountered this when fixing: https://bugs.eclipse.org/bugs/show_bug.cgi?id=221172
Comment 1 Paul Webster CLA 2010-03-19 07:49:33 EDT 
display.addListener(SWT.Skin, new Listener() {
  public void handleEvent(Event event) {
    System.err.println("New event for : " + event.widget);
  }
});

Skin events are fired for new widget construction, although some work has to be done to figure out that they have just been constructed.  Is there a simple way to check if this is the first Skin event for a widget?

PW
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:30: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.
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:34:52 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.