Script windows have a habit of the editor no longer functioning properly, always after a query has been executed at least once. Doesn't happen all the time but does happen regularly.
When "broken", all the number and letter keys function fine, but Enter, Delete, Backspace, Home, End, Tab and the arrow keys do not. Pressing delete for instance will usually pop up the "Unregister Server" prompt as if the Server list has focus. If within the Server list an item is highlighted that doesn't support being deleted/unregistered, nothing happens except the "Server" menu item flashes quickly. (I have found that if one clicks the Database dropdown within the editor, this keeps the Delete key from acting like it had focus on the Server list when you go back to editing. The key still doesn't work though.) Arrows keys will scroll the editor region, as if the scroll bar were focused, moving the viewable text but not moving the cursor within the editor. You can't delete text in the editor with either the delete key or backspace, but if you highlight the text with the mouse (but not with shift-arrow keys), you can type over it and replace the text, or delete it with the right-click menu Delete command. The Enter key will not create a new line of text... you have to cut-and-paste a newline character to create a new one. Home and End will move the cursor to the first or last line in the editor - instead of first or last char on the current line - but it doesn't move the cursor within the editor itself. TAB does absolutely nothing.
One editor being broken doesn't affect the others... they keep working fine. The broken editor never resumes working correctly though... you simply have to close it and open a new one. It happens pretty frequently unfortunately. It's been happening for quite some time - well before v23.0 for sure because I was hoping that release would fix it - but I'm not sure how long. It might have started happening after I upgraded to Ventura but I'm not certain of that either.
Below in the Support Information:
Hello Tim,
Done.
Btw, this issue seems related: https://www.aquaclusters.com/app/home/project/public/aquadatastudio/issue/15927
Done.
Btw, this issue seems related: https://www.aquaclusters.com/app/home/project/public/aquadatastudio/issue/15927
Aqua Data Studio does not longer present issues with MacOSX, please verify latest version builds and verify your current OS is supported.
Aqua Data Studio does not longer present issues with MacOSX, please verify latest version builds and verify your current OS is supported.
Please re-open. This issue is not fixed at all. It's a hassle daily and makes ADS difficult to recommend to my Mac using coworkers. Today I'm running MacOS Sonoma 14.5 and using ADS 23.2.
Happy to supply whatever details you need.
Please re-open. This issue is not fixed at all. It's a hassle daily and makes ADS difficult to recommend to my Mac using coworkers. Today I'm running MacOS Sonoma 14.5 and using ADS 23.2.
Happy to supply whatever details you need.
Problem still exists. No improvement.
Only thing I've learned since I originally opened the issue is that once the problem occurs you can temporarily fix it by changing servers. You don't actually have to "change" the server... you can reconnect to the same one, and doing so returns the editing functionality back to normal, at least until the next time you execute the query and then it likely becomes broken again. Such an annoying issue.
Problem still exists. No improvement.
Only thing I've learned since I originally opened the issue is that once the problem occurs you can temporarily fix it by changing servers. You don't actually have to "change" the server... you can reconnect to the same one, and doing so returns the editing functionality back to normal, at least until the next time you execute the query and then it likely becomes broken again. Such an annoying issue.
Nº do Problema15934 |
Reaberto |
Incompleto |
Finalização |
Nenhuma data de vencimento |
Nenhuma compilação reparada |
Nenhum tempo estimado |
Hello Tim,