>> 1. changes that are not saved to disk do not get respected - as >> opposed to other queries
> True, this feels confusing. Maybe it would be better to disable the test icon > if the current file has not been saved? Yes that would be less confusing (to me). > If you prefer to, you can enable the option »Save before executing files« in > the Preferences Dialog. This way, opened files will automatically be saved > before a query is run. Thanks, I did not know that. > 2. pressing the default button for running queries executes the most > recent query which is open in another tab > This is actually meant to be a feature: If lots of library modules are opened > in the editor, it can save a lot of time if you can execute the main module > that has been executed most recently. Ah - I can see the value - I always thought there is no other context for the play button than the current tab. Thanks, Daniel
