Small Python console glitch.

[Peter Parker]

Very minor ticket, but this is something I run into often while making small adjustments to scripts and testing them as I go. To reproduce:

1. Open up your favourite script in a MantidPlot Python Window.
2. Pressing Ctrl+Return will obviously execute the script.
3. Now, highlight some part of the script and press some alphanumeric keys.
4. Pressing Ctrl+Return immediately after making the edit now has no effect. The user must move the cursor, or go to "Execute"->"Execute Selection".

Nothing major at all, just a small usability point.

[Nick Draper]

http://www.mantidproject.org/Release_Notes_2_2_Full_List

[Nick Draper]

Moved to release 2.4

[Nick Draper]

Moved at the code freeze for release 2.4

[Nick Draper]

Moved to r2.6 at the end of r2.5

[Nick Draper]

Moved to the Backlog after the code freeze for R2.6

[Nick Draper]

bulk move to assigned at the into of the triage step

[Dan Nixon]

Cannot reporduce the original issue.

[Peter Parker]

I've tried this again in a Windows nightly build from 18 Nov, which is the most recent version I have installed. It is *still* an issue in that version. Perhaps it's been fixed since then but I don't think it's likely.

To clarify:

• Open up the script window.
• Type print "test"
• Hit Ctrl+Return to print "test" to the screen.
• Highlight the word "test" and type another test that will not work.
• Pressing Ctrl + Return will not work until you move the cursor again.

Those instructions have to be followed *exactly*. Maybe it's only a problem on Windows.

[Nick Draper]

I agree I was just writing this:

This is actually a bug, albeit a very minor one

Steps to reproduce:

1. put this in the script window

   print "hi"
   print 2+1
   print "bob"
   

2. With the cursor at the end hit ctrl and enter - it will run (if there is no selection Mantid is supposed to run everything)

Highlight and replace the middle line with a so the script looks like

print "hi"
a
print "bob"

1. before you click anywhere else hit ctrl+enter - nothing happens, but it should

[Nick Draper]

Found it!

[Nick Draper]

re #5272 Fix for script edit bug

Changeset: 265fc135dbb10d0e05b0ad9ff8379473aa24cb45

[Nick Draper]

To Test

see comments 12 and 13 for steps to reproduce

[Peter Parker]

This one still needs a quick checkbuild, Nick.

[Harry Jeffery]

Merge remote-tracking branch 'origin/feature/5272_scripteditor_wont_exec_after_selection_edit'

Full changeset: ​f597473a00a08373cc42385b136c4ff43e10a6f3

[Stuart Campbell]

This ticket has been transferred to github issue ​6118