|
Editing cells in DBISL's result set pane is a nice feature, and as expected, one can copy & paste the contents of the edited cell. However, that does not work for cells that have a NULL value currently: They do not accept pasted contents, independent of the fact whether the cell's displayed contents - "(NULL)" - is selected or not. In order to allow to paste contents, I have to click on the "Edit in window" command, and then it's possible to paste into the window or directly into the cell. That's somewhat uncomfortable... BTW: Are there keyboard shortcuts to activate the "Edit in window" and "Set to NULL" commands and the while I'm editing a cell? That would be a nice enhancement, as editing should generally be doable without mouse actions. Tested with 12.0.1.3554 on Windows 32-bit. |
|
For me editing a row and selecting the null cell and pressing ctrl-v inserts the clipboard text into that cell. Have I misundestood your approach? No, you have fully understood my situation - however, exactly that does not work for me, unless I use the "Edt in window" command. In contrast, inserting normal character does work, so it's really the CTRL-V command (and the according "Paste" command from the "Edit" menu) that is blocked/ignored. And if the cell is not null, then CTRL-V does work, too. The behaviour is the same for numeric, text or date/timestamp columns.
(28 Mar '12, 09:44)
Volker Barth
Replies hidden
Comment Text Removed
Sorry for the confusion, I have used dbisql v11.0.1. You are right with dbisql v12.0.1 I can reproduce your observation. You can press any char, afterwards also the ctrl-v works on the same cell (just a workaround).
(28 Mar '12, 10:30)
Martin
Thanks for the re-check - and yes, the workaround is a good one I had not thought of.... Note, it takes a "backspace" or other deletion to remote the inserted char right before the CTRL-V:) FWIW, CTRL-A does not work with NULL cells, either
(28 Mar '12, 10:36)
Volker Barth
|
Just to restate: According to Martin, the behaviour is different (and better) in 11.0.1. So may this be considered a bug or undesired behaviour in 12.0.1?
Any comment from the SQL Anywhere tooling engineers would be very welcome:)