You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I've tried setting multiple hotkey for one component, i.e. <Label value="Val1" hotkey="W,R" />. This works sometimes in the Labeling Interface preview. It stops working once you've edited the interface again, but works again after refreshing. Now the real fun part is: if you try to use such an interface via the data manager it doesn't load. Once you've done that, any task in any project opened thereafter in this browser window will not work. Force refresh/new window solves this issue, but only as long as you don't touch the multi-hotkey interface.
[{"text": "I'm a dummy text. Sooo... How are you? Good? Good."}]
Open/create a project with e.g. the example interface
load some dummy data
try to open a task
observe
open a task in another project with a different interface to see that it is now broken as well.
Expected behavior
Unclear whether multiple hotkeys per component should work, but would be great if they did. If they aren't supposed to, they at least shouldn't break everything.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
OS: Windows 11 64-bit
Label Studio Version: v2.4.8dev-16 (app.heartex Enterprise)
Browser:
Opera core: 98.0.4759.50
Chromium version:112.0.5615.165
A colleague verified the behavior on her MacBook I don't have more information about.
Additional context
Motivation was to provide our labelers with an alternate hotkey layout so they could switch to a (presumably better) one without breaking their current workflow.
Stack Trace
caught (in promise) TypeError: e.toUpperCase is not a function
at s (keymaster.js:33:27)
at t.key.unbind (keymaster.js:182:13)
at l (Hotkey.ts:147:11)
at Object.unbindAll (Hotkey.ts:333:7)
at Object.setupHotKeys (Annotation.js:771:15)
at be (mobx.module.js:928:19)
at r (mobx.module.js:915:16)
at mobx-state-tree.module.js:2593:35
at J (mobx-state-tree.module.js:2456:16)
at Object.r (mobx-state-tree.module.js:2483:16)
at Object.r (store.js:135:9)
at be (mobx.module.js:928:19)
at r (mobx.module.js:915:16)
at mobx-state-tree.module.js:2593:35
at J (mobx-state-tree.module.js:2456:16)
at Object.r (mobx-state-tree.module.js:2483:16)
at LSFWrapper.setAnnotation (lsf-sdk.js:442:10)
at LSFWrapper.setLSFTask (lsf-sdk.js:352:10)
at AppStore.js:228:19
at Generator.next (<anonymous>)
at mobx-state-tree.module.js:3631:41
at executeAction (mobx.module.js:928:1)
at res (mobx.module.js:915:1)
at runMiddleWares (mobx-state-tree.module.js:2593:22)
at runWithActionContext (mobx-state-tree.module.js:2456:1)
at wrap (mobx-state-tree.module.js:3617:1)
at onFulfilled (mobx-state-tree.module.js:3631:1)
The text was updated successfully, but these errors were encountered:
Describe the bug
I've tried setting multiple hotkey for one component, i.e.
<Label value="Val1" hotkey="W,R" />
. This works sometimes in the Labeling Interface preview. It stops working once you've edited the interface again, but works again after refreshing. Now the real fun part is: if you try to use such an interface via the data manager it doesn't load. Once you've done that, any task in any project opened thereafter in this browser window will not work. Force refresh/new window solves this issue, but only as long as you don't touch the multi-hotkey interface.To Reproduce
Example Interface & Dummy Data
Expected behavior
Unclear whether multiple hotkeys per component should work, but would be great if they did. If they aren't supposed to, they at least shouldn't break everything.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
A colleague verified the behavior on her MacBook I don't have more information about.
All Label Studio versions
Additional context
Motivation was to provide our labelers with an alternate hotkey layout so they could switch to a (presumably better) one without breaking their current workflow.
Stack Trace
The text was updated successfully, but these errors were encountered: