Bug 15984 - Activating help does not bring help window to front
Summary: Activating help does not bring help window to front
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: User Assistance (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 98
: P2 normal (vote)
Target Milestone: 2.0.1   Edit
Assignee: Konrad Kolosowski CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-14 17:46 EDT by Dave Thomson CLA
Modified: 2002-08-07 09:50 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Thomson CLA 2002-05-14 17:46:38 EDT
Run eclipse 0514
Help->Help Contents
Now bring eclipse workbench window to front.
Help->Help Contents
It flashes in the Windows task bar at the bottom of the window, but does not 
come to front.  It should come to the front.

NOTE:  If the help window is collapsed when you do this - it works!
Comment 1 Konrad Kolosowski CLA 2002-05-15 01:42:47 EDT
It is not immidiately obvious, bug help browser runs in a separate process from 
Eclipse.  It is the operating system that prevents application from stealing 
focus from another.  It is possible to change this behaviour using Microsoft 
Tweak UI.

This solution to run help browser as a separate process was chosen to solve 
modality problems in Eclipse 1.0, where help remained hidden when a modal 
dialog was open in Eclipse.  SWT could not provide a way to open a window that 
would not be independent of modality of others.  With current solution help 
correctly calls the SWT API that should cause window to come to front 
shell.forceActive();, but the final behavior is OS dependent.  See bug 12073 
and bug 13318 for related information.

The OS seems to bring to front application window that is opening first time or 
is being restored from minimized.  To exploit this fact to make help window 
always come to the front, would require always closing it or minimizing, which 
would result in much worse user experience.
Comment 2 Dave Thomson CLA 2002-05-15 12:48:14 EDT
The fact that the OS considers the help to be a separate process is a side-
effect of the way we decided to implement it.  The window *should* come to the 
front if eclipse is the application with a window at the front at that moment.

I discussed with MCQ, and we should defer this until after the 2.0 release, but 
leave it open, because I verified that Dreamweaver for example is able to make 
this work correctly and they also use IE for their help.
Comment 3 Dorian Birsan CLA 2002-07-17 21:56:41 EDT
We should investigate a solution that brings down the existing help viewer and 
opens it again.
Comment 4 Konrad Kolosowski CLA 2002-07-18 11:16:23 EDT
When minimizing the window and restoring it again puts it on top of other 
windows without OS preventing it.
Comment 5 Konrad Kolosowski CLA 2002-07-18 11:21:15 EDT
This trick does it:
			shell.setVisible(false);
			shell.setMinimized(true);
			shell.setVisible(true);
			shell.setMinimized(false);
It does not show window being minimized, and only when it restores, so it looks 
like we are opening a new window and replacing the old one.  No actual closing 
or opening help window occurs, which is good since closing openning a window 
would execute much longer and the visual effect would be worse.

I have relesed this code into head.  It should be included in the 2.0.1 release 
as well.