_From ccordoba12 on 2013-06-26T23:49:56Z_
As the "Continue" button has the shape of a play one, it seems some users are assuming it's the button they should use to run their files.
See here for a reference https://groups.google.com/d/msg/spyderlib/KvtAVn2Iqv8/ULwsaz0H9F8J
_Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1464_
_From ccordoba12 on 2013-12-11T12:47:02Z_
Labels: -MS-v2.3 MS-v2.3.1
_From ccordoba12 on 2014-07-10T20:05:43Z_
Labels: -MS-v2.3.1 MS-v2.4
This is less of an issue at least for the continue button, as it now looks like a fast forward icon, but in general there seems to be no reason to keep these icons visually enabled and clickable when not in debug mode. @dalthviz Maybe this fairly small enhancement could be part of your suite of debugger enhancements? I can't imagine it would be that hard to implement...
This is not so simple. The problem is the buttons state (enabled/disabled) need to be updated when users change focus from console to console. So we need to have a clear way to tell when a console is in debugging state, something we will only have with the new debugger.
Ah, I didn't consider the impact of multiple consoles with different states. I'll at least milestone this to betaX (since it will need the debugger) for the moment, and I suppose we can perhaps consider it after we've done more important things considering the rather small UI/UX improvement (as the original problem, the icon being confused, is no longer an issue) might not be worth the effort.
Do we want to create a beta3 milestone at this point, considering we're firming up what we want to do for it (the debugger, other funded stuff, and presumably smaller things?)
@dalthviz is this related to the work you started on this front? Can we close as duplicate?
@goanpeca yep I think it could be closed as duplicated of #10538