Early Access: DbVisualizer 6.5.10.7 is now available

I have tested keybindings in the new 6.5.10.7 EA version and it also suffers from the same keybinding bug. I have tested and found the following: (1) I have only tested on MacOSX 10.6.2, Intel x86_64, Java 1.6.0_17 (2) Only seems to be a problem for editor command "Extend Selection To End Of Line" (3) If I set a single binding of either Cmd+Shift+Right arrow (Mac default) or Shift+End then the binding works okay in either case (4) When I try and set a second binding so there are two then neither binding works in the editor So setting one binding alone is fine, but having two bindings set causes neither to work. I copied the MacOSX set for my own custom set. Oh and another minor issue is that the button text for the OK button in the Tool Properties dialog is "Ok" but it should be "OK" with an uppercase K since OK is an abbreviation. Apple use "OK" and indeed the Key Strokes dialog has an okay button with text "OK" so you are not internally consistent here. I would consider "Ok" as a bug.

Hi Roger, Yes I am adding a second key binding to the existing binding. I tried adding the new binding as a new binding by clicking the New Binding button and adding the keystroke instead of the Edit Binding button and this works correctly. So, err, what is the point of the second binding field in the bindings? Is it for combination keystrokes like used for generating some special symbols like say Alt+A A or some such? I found it rather confusing sorry. Perhaps i should have read the documentation!

Roger, I can confirm that the major freezing issue is not completely fixed in the EA version on MacOSX. I opened a connection to an oracle DB, opened the schema and clicked on a table to show the data. I came back to it ca 15 mins later and clicked on a different table, thereby causing DBV to call the database to get data to display. The app then freezes. The busy cursor appears and the GUI is unresponsive except for the menubar and the Stop Execution button in the Object view. The MacOSX force quit dialog shows DBV in red as 'not responding'. I clicked the Stop button. DBV remained frozen for a minute or so, maybe a bit longer. But eventually a message was shown saying the connection had been lost and containing a hyperlink "connect" to re-establish the connection. I clicked the link and it did recreate the connection and was then usable again. So this seems partially fixed! The only remaining issue is the time that the GUI is frozen for after I click the Stop button; it is too long. Having to wait for several minutes to proceed is no good for productive use if this happens frequently as in my case (for other readers I have a DB connection that seems to go stale after some minutes of inactivity).

Hi Timothy, Thanks for testing this. The behavior you describe is the intended (not perfect but the best that can be done). The Execution Timeout Value (the time you need to wait after clicking Stop in this case) is set to 60 seconds by default, because when we tried a similar approach earlier it turned out that a lower value caused problems for too many users. You can change it in Tool Properties, in the Database Connection category. Best Regards, Hans