Annoying things

I finaly took the time to post some very annoying things in plsql-developer (7.02.1076).
Not that the tool is all bad, but I thing these are some basic things every IDE should have.

1. search UP with short-cut key (eg shift-f3)

2. when having searched everything (after returning to the starting position) an alert should appear

3. when searching, you cannot delete the line (with ctlr-Y) )(because the text is selected)

4. when closing the browserpane, the tree is Collapsed

5. why are there no line numbers in an sql-window?

6. when jumping on a line (with ctrl-left, ctrl-right) the cursor doesn't jump where it suppose to

eg.
recX.name X:= X'something Xis XwrongX'X;

the X marks the position where the cursor should move (jumping from left to right)

7. when starting a comment with /* en hitting the return button, an * should appear on the next line
(i'm starting a comment)

8. the templates in de templates list should be linked to a keyboard shortcut or may be a seperate favorite template list binded to a keyboard shortcut.
for quick access; e.g we all use to_char(), dbms_output.put_line() or raise_application_error(,), ect ect all the time.

9. a new feature to duplicate the line where te cursor is on (often used by developers)

10. search/replace should search/replace ALL items in document (not starting from the cursor position)

...But there are also MANY positive things to mention; so keep up the good work!
Marcus
 
I think that 6 should read

recX.Yname X:= X'Ysomething Xis XwrongX'X;

where Y is additional places that I want the cursor to stop at.

for #7 I'd prefer that typing /* would produce an automatic /* X */ with the cursor at the X, then if I want a single line comment I just type and if I want multiple I press Enter first.

I recorded a macro to do #9, though I don't like the idea of losing what is alread in the clipboard to do it.
 
I have added this to the list of enhancement requests. One remark:
10. search/replace should search/replace ALL items in document (not starting from the cursor position)
There is a "Scope" option for this.
 
Since we're complaining... :)

Randy's numbers 2, 3, & 5 have annoyed me also. Here are 2 more.

It would be nice if when I type a call to a procedure the cursor would align to the parenthesis when I hit return.

For example:

Code:
procedure(param1
         |<--Cursor should go here.
It would be nice if the code contents wouldn't re-position the code window if it is right clicked. For example, I would like to copy a parameter name without moving to it.
 
Ah, but that would annoy me ;)

Probably is's an obsessive-compulsive condition I should really get looked at, but it bugs me when stuff that should line up, doesn't.

For example this drives me crazy:

Code:
proc_with_very_long_name ( param1
                         , param2 );

shortername ( param1
            , param2 );
Clearly it should LINE UP

Code:
proc_with_very_long_name
    ( param1
    , param2 );

shortername
    ( param1
    , param2 );
Of course this is a novel concept to the authors of the code beautifier.
 
William,

No worries - the comma's are put under the left parenthesis in both cases so we'd both be happy.

I think it would be nice if the tab would stop at left parentheses or if we hit return after a left parenthesis it lined up. The second option might be harder if there are multiple left parentheses though.

Currently, I hit tab until I'm in the area and have to back up a few spaces. After the first comma, it all lines up nice.

Mike
 
Back
Top