Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 92198

Summary:	Launched RCP application window cannot be activated
Product:	[Eclipse Project] JDT	Reporter:	Ryan Lowe <ryanlowe>
Component:	UI	Assignee:	Andre Weinand <andre_weinand>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	major
Priority:	P3
Version:	3.1
Target Milestone:	---
Hardware:	Macintosh
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:	stalebug

Description Ryan Lowe

2005-04-21 05:59:48 EDT

I'm not sure where this bug should go, I based the Product and Component off of
bug 23820.  Apologies if this is a dupe -- I searched for various things and
didn't find a match.

I'm using Eclipse 3.1M6 on Mac OS X and I made a launch configuration for a Rich
Client Platform (RCP) product.  The product does launch but there are many problems:

- the product's window appears *behind* the Eclipse window (like bug #23820)
- the product's window cannot be moved
- the product's window cannot be resized
- the product's window cannot be activated when I try to select it
- the product's menu (top of screen) does not replace Eclipse's menu, probably
because the window cannot be activated/selected
- the launched product can only be minimized, maximized or closed
- the product does not appear in the Dock or Alt-Tab menu.  Should it?  If the
product's window is supposed to be grouped with Eclipse, Expose does not know this.

NOTE: I tried launching the product as an application instead and the same
problems occur.

This launching problem makes RCP application development very difficult on the
Mac.  My only other option is to build my complete RCP product with my Ant
scripts and launch it from the Finder.

Comment 1 Andre Weinand

2005-04-21 09:54:07 EDT

You are probably missing the -XstartOnFirstThread argument somewhere...

However, Eclipse should take care of this automatically.
So could you please list the detailled steps of how you made a launch configuration for a Rich Client 
Platform (RCP). Without them I cannot reproduce the problem.

Comment 2 Ryan Lowe

2005-04-21 10:46:46 EDT

1. I have a product that is detected by Eclipse (defined by extension).  When I
make the new launch configuration, this product is in the "Run a product"
dropdown menu and I select it.

2. Then I switch to the plugins tab, deselect all projects and then select only
those plugin projects I need for the product.

3. Run the launch configuration.

On Windows these steps work fine.  I wasn't aware that I had to do anything else
on the Mac...

---

This problem is happening with an open source project I am working on, so if all
else fails you could check it out from CVS: http://sourceforge.net/projects/durham.

I don't expect you will have to do this, I just thought I would give you the option.

Comment 3 Ryan Lowe

2005-04-21 10:51:40 EDT

I should also mention that I change the Target Platform in Eclipse.  I do this
because the RCP application uses stable Eclipse 3.0.2 as a platform and I use
the latest milestone (3.1M6) for development.

I have an Eclipse project containing the Eclipse 3.0.2 plugins and I point the
Target Platform to this project before I run the launch configuration.

Comment 4 Ryan Lowe

2005-04-21 11:20:04 EDT

If I explicitly put "-XstartOnFirstThread" into the VM Arguments text box it
does not fix the problem.

Comment 5 Ryan Lowe

2006-05-17 12:18:06 EDT

With Mac OS X 10.4 and Eclipse 3.2RC4 this problem no longer happens, so I'm OK with you closing this bug.

Even better, my RCP apps work "out of the box" on Mac OS X.  No additional arguments were needed (like comment #1).  Good work, guys.

Comment 6 Eclipse Genie

2019-12-20 08:16:51 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.

--
The automated Eclipse Genie.