Hello,
I find something really annoying, both with Program and SQL Windows.
Whenever several tabs are present and we execute the content of one of these windows, the last tab becomes activated. Could this be changed to become the first tab?
An example: every of our package / package body files ends by a "show errors" line. Notwithstanding the fact that "show errors" is considered as an error when we compile it (though it is actually compiled) - Marco assured this would be fixed -, the tab containing it is selected and we have to reselect the previous tab. (Is it really the last tab or the one where an error was found? If this is the latter, then solving the bug will also resolve this slight inconvenience.)
Regarding SQL windows, whenever I create a file containing several SQL statements that I want to execute as a set, the idea is to see the result of the first query, then the second, and so on... However, since the very last result set is selected, I have to manually go back (something needing to scroll) to the first one set after each execution.
As I said, this is not a major bug, this is just a question of usability in an already largely user-friendly product.
Thanks in advance for your remarks.
Best regards.
Avigael
I find something really annoying, both with Program and SQL Windows.
Whenever several tabs are present and we execute the content of one of these windows, the last tab becomes activated. Could this be changed to become the first tab?
An example: every of our package / package body files ends by a "show errors" line. Notwithstanding the fact that "show errors" is considered as an error when we compile it (though it is actually compiled) - Marco assured this would be fixed -, the tab containing it is selected and we have to reselect the previous tab. (Is it really the last tab or the one where an error was found? If this is the latter, then solving the bug will also resolve this slight inconvenience.)
Regarding SQL windows, whenever I create a file containing several SQL statements that I want to execute as a set, the idea is to see the result of the first query, then the second, and so on... However, since the very last result set is selected, I have to manually go back (something needing to scroll) to the first one set after each execution.
As I said, this is not a major bug, this is just a question of usability in an already largely user-friendly product.
Thanks in advance for your remarks.
Best regards.
Avigael
