V-8 bugs

[carabazz]

1. Ctrl-F keystroke does not work
2. PL/Shortcuts does not appear in the plug-ins
3.
3.1. Open and connect, open few packages from a database
3.2. Close
3.3. Open and do not connect.
3.3.1.Windows list is frozen without any window names being visible
3.4. Close
3.5. Open and connect
3.5.1.Packages previously opened from the database disappear from the Window List

 

[Claus Pedersen]

I have also experienced 1. when installing ver. 8 on top of ver. 7.1

It seems like the only shortcut that disappeared. It is easy to fix, though: Tools -> Preferences -> User Interface -> Key Configuration -> Edit / Find Replace -> assign Ctrl-F

 

[WexSoft]

Hi Folks

I found that the easiest way to restore all the shortcut keys is

Tools -> Preferences -> User Interface -> Key Configuration, then click the Reset to Default... button - this will restore all shortcut keys, and you can then edit them as you require.

Best regards

Billy

 

[Marco Kalter]

1. Ctrl-F keystroke does not work

This is indeed an upgrade bug. You need to assign the key through Tools > Preferences > Key configuration as stated above.

2. PL/Shortcuts does not appear in the plug-ins

The PL/Shortcuts Plug-In is incompatible with PL/SQL Developer 7.1 and later, and unfortunately the Plug-In is no longer supported by the 3rd party author. However, you can use the built-in AutoReplace functionality instead (Tools > Preferences > Editor).

3.

We'll check it out.

 

[PeterW]

I found that the easiest way to restore all the shortcut keys is

Tools -> Preferences -> User Interface -> Key Configuration, then click the Reset to Default... button - this will restore all shortcut keys, and you can then edit them as you require.

Great tip! Thanks.

 

[vlevi]

I have many problems with version 8. I have used version 6 before, and many "enhancements" looks like bug for me
- Decimal characters appears with wrong syntax highlight. For example, nvl(j.sumvalue,2.15) , instead of nvl(j.sumvalue,2.15) Maybe it happens, because my Regional setting (in Windows) uses comma for decimal separator, instead of a dot. But, for developement, of course I have to use the dot character.
- Very annoying thing is, the behavior of the Ctrl+Backspace. I know, it was changed in version 7, but it is still "wrong" in ver8. When I press Ctrl+Backspace in ver6, it deletes the word, where I am, and leaves the space before the deleted word (exactly the same way, as this editor is, where I write this post ) In Ver8, Ctrl+backspace deletes the word and the space character before, so I need to re-enter the space. For example, "select * from my_table wgere" I press Ctrl+Backspace to delete the "wgere" word, and re-enter it correctly "where".
- The other problem is with Ctrl+Backspace, the deletion of comma separated values. For some reason, ver8 deletes the commas only, and the word in a separate step. But with the space, again . Try to delete with Ctrl+Backspace this line, you will understand me. "Values(pn_Torzsszam, mr_szerz.n_SzerzSzam, pn_AktEv, pn_AktHo, mr_szb.n_BesBer, "
- Behavior of Page up, Page Down. In ver6, these keys advanced the editor window one page up and down, as desired. In ver8, the cursor moves about 1 page up and down, and scrolls the editor to make the cursor nearly visible. Try to push a page down, and immediately a page up in Ver6, and Ver8, you will see the difference. In ver8, nothing happens, if the cursor is in the first/last line! Ver6 works fine, as desired.
- Font rendering is terrible. Look the difference between the ver6 and ver8 screenshots
Editor window images

 

[carabazz]

Much appreciated, guys. 1 and 2 are solved.

 

[carabazz]

The PL/Shortcuts Plug-In is incompatible with PL/SQL Developer 7.1 and later, and unfortunately the Plug-In is no longer supported by the 3rd party author. However, you can use the built-in AutoReplace functionality instead (Tools > Preferences > Editor).

Edit an existing line of code anywhere in the middle/beginning, type a shortcut immediately before a "non-space" character then hit Space/Enter, AutoReplace doesn't fire up.

 

[Marco Kalter]

Decimal characters appears with wrong syntax highlight. For example, nvl(j.sumvalue,2.15) , instead of nvl(j.sumvalue,2.15) Maybe it happens, because my Regional setting (in Windows) uses comma for decimal separator, instead of a dot. But, for developement, of course I have to use the dot character.

I cannot reproduce this, regardless of the decimal point setting.

- Very annoying thing is, the behavior of the Ctrl+Backspace. I know, it was changed in version 7, but it is still "wrong" in ver8. When I press Ctrl+Backspace in ver6, it deletes the word, where I am, and leaves the space before the deleted word (exactly the same way, as this editor is, where I write this post smile ) In Ver8, Ctrl+backspace deletes the word and the space character before, so I need to re-enter the space. For example, "select * from my_table wgere" I press Ctrl+Backspace to delete the "wgere" word, and re-enter it correctly "where".
- The other problem is with Ctrl+Backspace, the deletion of comma separated values. For some reason, ver8 deletes the commas only, and the word in a separate step. But with the space, again smile. Try to delete with Ctrl+Backspace this line, you will understand me. "Values(pn_Torzsszam, mr_szerz.n_SzerzSzam, pn_AktEv, pn_AktHo, mr_szb.n_BesBer, "

We'll see if we can improve this. I'm sure others will complain as soon as we change this though.

- Behavior of Page up, Page Down. In ver6, these keys advanced the editor window one page up and down, as desired. In ver8, the cursor moves about 1 page up and down, and scrolls the editor to make the cursor nearly visible. Try to push a page down, and immediately a page up in Ver6, and Ver8, you will see the difference. In ver8, nothing happens, if the cursor is in the first/last line! Ver6 works fine, as desired.

Movement is okay. I suppose we could center the cursor position after movement.

- Font rendering is terrible. Look the difference between the ver6 and ver8 screenshots

I cannot reproduce this. Which font are you using?

 

[Marco Kalter]

Edit an existing line of code anywhere in the middle/beginning, type a shortcut immediately before a "non-space" character then hit Space/Enter, AutoReplace doesn't fire up.

We'll enhance this.

 

[vlevi]

"Decimal characters appears with wrong syntax highlight. "
But, believe me, it went wrong somewhere. Ver6 look good.

"I cannot reproduce this. Which font are you using?"
Does not matter. For example, Consolas, or Courier New, 10pt. Comments are italic, and clearly looks that 1-2 pixels are missing from the right sides of the characters. Or the left side covers the previous character, I don't know.

"Ctrl Backspace"
I've tried to use PL/SQL Developer 8 to edit source code. Much worse than with ver6. Ver6 is okay, but ver8 is unusable for editing 1000s of lines of source.

"Page up and down".
I think it's not a solution, if you position the cursor on the center. The cursor's onscreen position should not be changed after a page down. Again, I must say, it should behave exactly this forum editor does

Font problems

Font is OK

 

[Worker]

Decimal characters appears with wrong syntax highlight. For example, nvl(j.sumvalue,2.15) , instead of nvl(j.sumvalue,2.15)

I cannot reproduce this, regardless of the decimal point setting.

I reported this here as well and you said it'd get fixed. If you paste "2.15" into a program window, everything is fine. However, if you type "2.15", then only the "2" gets syntax highlighted as a number.

 

[vlevi]

it's strange. If you press enter on the line, which contains these numbers, it appears correctly. But during typing, it shows, that something is wrong with syntax.
For many reasons, I must say, that the editor of the Ver6 PL/SQL Developer is much-much better.
The only editor improvement for me is the autoreplace.

 

[Marco Kalter]

Okay, we'll check it out.

 

[vlevi]

Some other, very strange behavior.
In version 6, the during debugging, the wait cursor appeared, while I had to wait for something (e.g. to finish a procedure running).
In version 8, the wait cursor isn't there, so I do not know, what's happening. Okay, I can see, that the debugging buttons are dimmed, or not, but I do not know, what else I can do during debugging, that wait to finish something.
Bit, for example, the compilation of invalid objects locks SQL Developer, but this is a process, which could be run "in the background"
And other, very old problem with recompilation, which can be seen in all versions of PL/SQL Developer. It recompiles everything, even if it became valid during recompilations. For example, if procedure_a calls procedure_b, and both are invalid, the recompilation of procedure_a also recompiles procedure_b, so no need to recompile procedure_b again. Moreover, if I recompile procedure_b, the procedure_a becomes invalid, so I need to recompile it again.

 

[Marco Kalter]

In version 8, the wait cursor isn't there, so I do not know, what's happening. Okay, I can see, that the debugging buttons are dimmed, or not, but I do not know, what else I can do during debugging, that wait to finish something.
Bit, for example, the compilation of invalid objects locks SQL Developer, but this is a process, which could be run "in the background"

We'll check it out. It may be that the cursor shape is incorrect when it is over the editor.

And other, very old problem with recompilation, which can be seen in all versions of PL/SQL Developer. It recompiles everything, even if it became valid during recompilations. For example, if procedure_a calls procedure_b, and both are invalid, the recompilation of procedure_a also recompiles procedure_b, so no need to recompile procedure_b again. Moreover, if I recompile procedure_b, the procedure_a becomes invalid, so I need to recompile it again.

Recompilation occurs in order of dependencies, so this should not happen. We'll check it out though.