For some subjects we've disabled the default CRUD elements and replaced it by tasks.
For the ‘Edit’ I can assign Ctrl + E to “override” the default edit shortcut. However, for the add and delete I cannot select the + and - sign. The Ascii code table is unfortunately read only. Is this somehow possible to do?
It would make more sense to our users the shortcuts are generic and not mixed (Ctrl+- and Alt+X for example). I'm aware that this idea would probably fix our problem, but I don't really expect that to be implemented soon.
Best answer by Mark Jongeling
Hi René,
I have added the keycode into the Ascii table through SQL code but it seems the GUI does not recognize that it should now activate a Task instead of the GUI add button. So it is not possible.
What does seem to work is adding keycode 187 which is the + (=) character that is beside the Backspace key. However, I don't recommend doing that as the GUI will then tell the shortkey is:
OemPlus = + key next to Backspace
We do have the Idea of CRUD tasks high on the backlog so there's a good chance we'll implement it with the 2021.3 release as this is a great idea that is wished for by many.
I have added the keycode into the Ascii table through SQL code but it seems the GUI does not recognize that it should now activate a Task instead of the GUI add button. So it is not possible.
What does seem to work is adding keycode 187 which is the + (=) character that is beside the Backspace key. However, I don't recommend doing that as the GUI will then tell the shortkey is:
OemPlus = + key next to Backspace
We do have the Idea of CRUD tasks high on the backlog so there's a good chance we'll implement it with the 2021.3 release as this is a great idea that is wished for by many.
I have ascii code ‘f5’ assigned to a task, but when I hit the button in the application, the task does not start. When I chose a different ascii code, there is no problem. Is this the same problem as you mentioned before? It is possible to select ‘f5’ as ascii code, so if so, that seems like an issue to me.
I have ascii code ‘f5’ assigned to a task, but when I hit the button in the application, the task does not start. When I chose a different ascii code, there is no problem. Is this the same problem as you mentioned before? It is possible to select ‘f5’ as ascii code, so if so, that seems like an issue to me.
F5 is often used for refreshing data, not only in the Thinkwise platform (your browser for example). You’re really sure you should use that as a shortcut for a task?
Thanks for your response René, I have tried this and this is working! Still this feels like a workaround, since ascii code f5 is available to use as shortcut. @Mark Jongeling is this something Thinkwise will fix?
Thanks for your response René, I have tried this and this is working! Still this feels like a workaround, since ascii code f5 is available to use as shortcut. @Mark Jongeling is this something Thinkwise will fix?
Difficult to say because currently our GUI's are not expecting this. F5 is bounded to Refreshing a subject, which is hardcoded into the GUI most likely, however we can't disallow the option of select F5 as shortkey as combining it with Shift for example is legitimate.
We do have default validations for this:
Validations for checking GUI shortcuts being used as shortkeys for objects
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
