Community
Participate
Working Groups
* open a msword doc in place * open a bmp file in place * ensure the bmp editor is active * click on the navigator * click on the tab for the .doc editor Observe a bunch of flashing occurs and you can even see it repaint the bmp editor, draw its toolbars etc, then remove them NOTES:
PRODUCT VERSION: 109 jre
Please ensure that this is fixed for 2.0
The flashing when switching to the .doc editor is fixed. However, when switching from the .bmp editor to the Navigator view, the editor is not always deactivated. It switches from showing the editor (MS Paint) to a bmp viewer but keeps the editor tab activated most of the time.
Revisit post v2
Revisit
Not sure if this is still a problem. Can't reproduce it now due to bug 27126.
Knut, I can't reproduce what you described in Comment #3. Could you add some screen shots, not sure if I undestand what you mean. If you can't reproduce I will close as FIXED since the original problem was fixed.
I can still reproduce this the first time I switch to the Navigator after opening a bmp or doc file inline. After opening the bmp file the image editor has focus. When I click in the Navigator the editor still has focus even though I can scroll around the Navigator. This only happens when switching from the editor to the Navigator without Eclipse losing and regaining focus in between. I.e., Open the bmp file and without doing anything else click the navigator. Also, if you click the Navigator title bar it won't get focus but if you select a Navigator item you can scroll in the Navigator using the keyboard.
Created attachment 2611 [details] Screen shot Note the active/focus Navigator selection and the editor focus.
The original problem is fixed. The problem described in the comments #8 and #9 seems to be an SWT problem. SWT should fire and SWT.Activate event when we click in the Navigator label or tree since the focus is in the OLE file. Since we do not get and Activate event the Navigator is not activated.
Veronika to investigate and advise the problem described in comment #8
Veronika, does this still happen? Are we really not sending the SWT.Activate?
To verify this, I need to write a wad that reports the events and try this. Unable to confirm just be using Eclipse. I do not believe this has changed.
The problem described is a bug which will not be fixed in the current version of eclipse. If you would like to contribute a fix for this problem, please attach a patch file and reopen this bug report.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.
