Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 525688 - [OSX] SWT menus completely inactive
Summary: [OSX] SWT menus completely inactive
Status: CLOSED DUPLICATE of bug 426062
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.4.1   Edit
Hardware: Macintosh Mac OS X
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-06 11:49 EDT by Marti Verdugo CLA
Modified: 2018-01-05 05:02 EST (History)
1 user (show)

See Also:


Attachments
The attached class is creating the menu items in question (46.70 KB, application/octet-stream)
2017-10-06 11:49 EDT, Marti Verdugo CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marti Verdugo CLA 2017-10-06 11:49:33 EDT
Created attachment 270870 [details]
The attached class is creating the menu items in question

I have a standalone SWT application.  The menu items are just completely inactive. When I click the menu bar, nothing happens. This includes both menus created with SWT.CASCADE and SWT.PUSH. This used to work.

If I click JUST ONCE in any Eclipse window, then the menus in my completely separate SWT application start working.  They continue working until I restart my application, after which I must click in Eclipse again.  How are my actions in the Eclipse application affecting my independent process.

I am running OSX El Capitan version 10.11.6.  

I am willing to upgrade to a new version of SWT but none of the maven repos I can fund seem to have a newer version for MacOS.
Comment 1 Lakshmi P Shanmugam CLA 2017-11-16 03:16:23 EST
Sounds related to Bug 426062. Can you please try with a recent Eclipse/SWT version like Oxygen (4.7)? You can find the SWT downloads at the bottom of the page - http://download.eclipse.org/eclipse/downloads/drops4/R-4.7.1a-201710090410/
Comment 2 Lakshmi P Shanmugam CLA 2018-01-05 05:02:17 EST
This sounds very similar to Bug 426062 which has been fixed in 4.4.2. Please reopen if you still see the problem with 4.4.2 or recent version of Eclipse?

*** This bug has been marked as a duplicate of bug 426062 ***