I like (I think) the fact that PL/SQL Developer now remembers my last cursor position for each package I've looked at. However, it doesn't mesh well with the existing functionality of "Find Database Objects".
For example:
1) Use "Find Database Objects" to search for "is_bit_set" in SYS' Package Specifications.
2) Double-click on the found package: SYS.DBMS_UTILITY.
3) Notice that "is_bit_set" is highlighted.
4) Click BELOW the "is_bit_set" function and then close the program window.
5) Double-click again on the found package: SYS.DBMS_UTILITY.
6) Notice that "is_bit_set" is now not highlighted.
It depends on where your last cursor position was. If it was above the thing that you searched for, then it will be highlighted. If it's below it, then it will use your last cursor position.
I'd like to request 2 things:
1) A user option to turn off the position-remembering. (It gets in the way when you have packages with the same name but different content for different users.)
2) Double-clicking a "Find Database Objects" result should always ignore the last cursor position.
For example:
1) Use "Find Database Objects" to search for "is_bit_set" in SYS' Package Specifications.
2) Double-click on the found package: SYS.DBMS_UTILITY.
3) Notice that "is_bit_set" is highlighted.
4) Click BELOW the "is_bit_set" function and then close the program window.
5) Double-click again on the found package: SYS.DBMS_UTILITY.
6) Notice that "is_bit_set" is now not highlighted.
It depends on where your last cursor position was. If it was above the thing that you searched for, then it will be highlighted. If it's below it, then it will use your last cursor position.
I'd like to request 2 things:
1) A user option to turn off the position-remembering. (It gets in the way when you have packages with the same name but different content for different users.)
2) Double-clicking a "Find Database Objects" result should always ignore the last cursor position.
