Bug 506871 - Engine switch button not working reliably
Summary: Engine switch button not working reliably
Status: CLOSED MOVED
Alias: None
Product: Ease
Classification: Technology
Component: UI (show other bugs)
Version: 0.3.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 459676
Blocks:
  Show dependency tree
 
Reported: 2016-11-02 02:23 EDT by Markus Duft CLA
Modified: 2023-11-20 13:30 EST (History)
1 user (show)

See Also:


Attachments
Screencast of failure (420.78 KB, video/mp4)
2016-11-02 02:23 EDT, Markus Duft CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Duft CLA 2016-11-02 02:23:15 EDT
Created attachment 265149 [details]
Screencast of failure

In 0.3.0, choosing a different engine does not reliably switch to that engine, multiple clicks on the button itself and the drop down menu are required. I recorded a screencast for clearity.
Comment 1 Christian Pontesegger CLA 2016-11-02 17:22:08 EDT
You are facing a focus issue here. When the shell view does not have focus we cannot set/change the script engine. This is a problem as a click on a toolbar button does not change the focus on the views. As we can have multiple shell views we do not know on which view to set the engine. I guess there is nothing we can do from our side here.
Comment 2 Markus Duft CLA 2016-11-03 02:39:39 EDT
The button itself has no idea to which view it belongs? Wouldn't it be possible to at least display a message, or do /something/ except for silently doing nothing?
Comment 3 Christian Pontesegger CLA 2016-11-03 14:36:47 EDT
you are right, we could open a messagebox informing the user to activate the view first. To me this seems like a platform UI bug that a view does not get focus when one of its toolbar buttons gets clicked
Comment 4 Markus Duft CLA 2016-11-04 03:30:15 EDT
True. If this happens on linux only, and windows behaves "correct", then this sounds like a different bug :) In this case, let's wait until we get response on 459676.
Comment 5 Frederic Gurr CLA 2023-11-20 13:30:10 EST
This issue has been migrated to https://gitlab.eclipse.org/eclipse/ease/ease/-/issues/87.