We have a user request to allow them to customize hotkeys. We allow some of this in the HistomicsUI config file. They want it to be per-user. We need to have a dialog showing what can be redefined (and groups are flexible, so this might necessarily be dynamic) and allow them to define what they like. In the ideal, we'd even allow all of the geojs core keys to be remapped (default for instance is left/ctrl-shift-left/shift-left to jump the image pixel/short/long, and they might want to change that).
I think we'll need to store this either (a) in a file in the user's private folder or (b) on the user document itself. The virtual of (a) is that it could be a user editable.
We might just want this to be the same .histomicsui_config.yaml and alter large image's config endpoint to search up the folder tree and use the global, but then ALWAYS fuse a user's Private/ file IF it exists. One defect to that is that it would conflict with use a private-folder-specific config FOR that purpose, so we probably should discuss this.
We definitely WANT the UI for this, even if we could do all the configuration from the config file.
We have a user request to allow them to customize hotkeys. We allow some of this in the HistomicsUI config file. They want it to be per-user. We need to have a dialog showing what can be redefined (and groups are flexible, so this might necessarily be dynamic) and allow them to define what they like. In the ideal, we'd even allow all of the geojs core keys to be remapped (default for instance is left/ctrl-shift-left/shift-left to jump the image pixel/short/long, and they might want to change that).
I think we'll need to store this either (a) in a file in the user's private folder or (b) on the user document itself. The virtual of (a) is that it could be a user editable.
We might just want this to be the same
.histomicsui_config.yamland alter large image's config endpoint to search up the folder tree and use the global, but then ALWAYS fuse a user's Private/ file IF it exists. One defect to that is that it would conflict with use a private-folder-specific config FOR that purpose, so we probably should discuss this.We definitely WANT the UI for this, even if we could do all the configuration from the config file.