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

Bug 325948

Summary: Quick Editor and editor actions incorrectly disabled transiently
Product: [Eclipse Project] e4 Reporter: Hitesh <hsoliwal>
Component: UIAssignee: Project Inbox <e4.ui-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: daniel_megert, deepakazad, remy.suen
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
Screenshot none

Description Hitesh CLA 2010-09-22 07:52:21 EDT
Created attachment 179369 [details]
Screenshot

A new selection event seems to fix the problem. See attached screenshot.
Comment 1 Remy Suen CLA 2010-09-22 08:05:56 EDT
This seems to only be a problem if you have breadcrumbs turned on.
Comment 2 Remy Suen CLA 2010-09-28 14:57:37 EDT
I believe the cause of this problem is similar to the issue reported by bug 325834. When you swap between editors, the breadcrumbs bar gets the focus instead of the editor itself. Then, as stated in comment 0, the window's tool items will enable itself once you activate editor.
Comment 3 Deepak Azad CLA 2010-09-29 02:47:30 EDT
> A new selection event seems to fix the problem.
Do you have a fix?
Comment 4 Hitesh CLA 2010-09-29 05:02:10 EDT
(In reply to comment #2)
> I believe the cause of this problem is similar to the issue reported by bug
> 325834. When you swap between editors, the breadcrumbs bar gets the focus
> instead of the editor itself. Then, as stated in comment 0, the window's tool
> items will enable itself once you activate editor.

(In reply to comment #3)
> > A new selection event seems to fix the problem.
> Do you have a fix?

Yep the breadcrumb seems to be the reason for this behaviour. This does look similar to bug 325834.
Comment 5 Remy Suen CLA 2010-11-01 14:08:33 EDT
This should be fixed now.

If your focus is on the breadcrumb then those items will be disabled. The behaviour is identical to 3.x.

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