Hi TOAD Community, I really like TOAD 12 x64 after having to use the old 32-Bit Version 9.6 for 8-9 years My employee at least decided to upgrade to 12.12. Very good! After using it for some time, I must say it's really OK, but of course there are still some flaws, so Quest (Dell?) developers have some work to do [:D] With Intellisense I like to use named notation for PL/SQL procedure/function calls. So I often use intellisense to pick a procedure from a package, and after I provide the "open" parantheses '(', TOAD presents the available signatures to be browsed. I select one and let Toad fill in the prototype, like shown below, TOAD will automatically select the first param ("State 1" below, selection is shown in bold on yellow). Since I hate UPPERCASE text except for symbolic constants, I try and select all uppercase text and hit CTRL+L to "lower" it. But this will destroy nearly the whole line, leaving only half of the the first argument intact, like shown in this three : State I: After selecting the prototype, TOAD has selected the 1st argument (bold on yellow background) begin utility_package.get_view_def(P_VIEW_NAME => P_VIEW_NAME IN VARCHAR2 , P_VIEW_DEF => P_VIEW_DEF OUT CLOB, P_VERBOSE => P_VERBOSE IN BOOLEAN) end; / State II: I extend selection in order to press CTRL-L afterwards, selection is again shown bold on yellow: begin utility_package.get_view_def( P_VIEW_NAME => P_VIEW_NAME IN VARCHAR2, P_VIEW_DEF => P_VIEW_DEF OUT CLOB, P_VERBOSE => P_VERBOSE IN BOOLEAN ) end; / State III: After I hit CTR+L , this is what is left; everything following the first "=>" is gone. Too bad! begin utility_package.get_view_def(p_view_name =>[CURSOR positioned here] end; / Of course I have checked the TOAD config options "Use lowercase characters after selecting elements from intellisense" as one of my fist configuration steps, since - like I said before - I HATE UPPERCASE letters crying at me. I expected this "use lowercase" option to be honoured for named notation also, but it isn't.. Question 1: Is the "fragility" shown above a known problem with TOAD 12, or is there something I'm doing wrong? Question 2: In future versions, will there be a lowercase option available for named notation prototypes ? Thanks in advance for your opinions and tips ...
↧