On Sun, Feb 10, 2013 at 5:43 AM, Pierre Raybaut <[email protected]>wrote:
> There is a similar problem with the editor plugin: multiple editor > widgets may be visible at the same time, and it should happen more > often than for consoles. The solution with the editor plugin was to > keep track of the last editor widget which had focus. This widget is > considered as the current active widget (e.g. new files will be opened > in that widget). > > So I guess that the same behavior should be expected for consoles: > this is your second solution. However, I'm not sure to understand why > you wrote that it would imply for the user to systematically click on > the console before executing the command: for me, as I understand it, > the user would simply click on the console once, to make it active. > > -Pierre > Ok, I have implemented the above described behavior. Instead of using current visibility, Spyder will now send requests to execute code to the last console that had focus. It will also use the same logic to determine where to send debugging control commands. It took a little bit of extra work to get this to behave in a sane way when the Console or the IPython console dockwidgets are floating outside the main window. But I think it is now well behaved. The relevant commit is here: http://code.google.com/p/spyderlib/source/detail?r=adb16b1c7119257a068dc94f4e51cb2e45d91de8 Code review and testing, as always, is much appreciated. Jed -- You received this message because you are subscribed to the Google Groups "spyder" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/spyderlib?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
