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

Bug 368881

Summary: Unable to keep event loop while no window visible
Product: [Eclipse Project] Platform Reporter: Thomas Schindl <tom.schindl>
Component: UIAssignee: Thomas Schindl <tom.schindl>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: david_williams, emoffatt, remy.suen, wlai
Version: 4.2   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard: stalebug

Description Thomas Schindl CLA 2012-01-17 16:04:57 EST 
In 3.x one was able to keep the application alive without any visible window (see http://lokeshshah.wordpress.com/2005/11/14/tray-icon-in-eclipse-rcp/) to e.g. move the application to the system tray and bring it up once more from there.

There are 2 problems:
a) WBWRenderer blindly sets the IWindowCloseHandler => one is unable to intercept 
   it and e.g. cancel the closing and simply hiding the shell instead

b) PartRenderingEngine someAreVisible() is checking for isVisible so in case 
   there's only an invisible window it will terminate the event loop

This is a feature loss when developing pure e4 applications against writing RCP-Apps in 3.x
Comment 1 Eric Moffatt CLA 2012-01-17 16:23:52 EST 
This makes sense to me...most especially we shouldn't be using the 'visible' flag to control the event loop in any case.
Comment 2 Eric Moffatt CLA 2012-04-04 14:09:16 EDT 
Tom, if I just change the logic to use the TBR rather than the visible flag do you think that would cover off the issues ??
Comment 3 Thomas Schindl CLA 2012-04-10 06:54:49 EDT 
probably yes - if you attach a patch I can take a closer look
Comment 4 Lars Vogel CLA 2019-11-14 03:21:10 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.