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
Hi @ClarkGuilty , not sure if this is a local problem or a problem encountered by others, but the keyboard shortcuts to go to the next / previous mosaic do not seem to work for the mosaic tool. I've tested other keys than the ones recommended (f, d, j, k) but without any success. I've not tested the single-image tool but I can if this is useful or let me know if you have any suggestion of things i should do to help you identify the origin of the problem.
I am running the QT-tool in a dedicated python environment (cf README), on a Macbook-pro from 2018 ... (Os Ventura 13.6).
No hurry to fix this but I wanted to report it in case other users would face the same problem.
The text was updated successfully, but these errors were encountered:
So far, it looks like this bug only affects OsX users. Due to system defaults, Macs immediately focus on the text-box of the page counter (the one used to change the page) and do not unfocus automatically when you click something else. So, when you use the shortcuts, the app interprets it as writing on the text-box, and not as a command.
We are experimenting with explicitly unfocusing the page counter, instead of relying on the system defaults. But it's still a work in progress.
Hi @ClarkGuilty , not sure if this is a local problem or a problem encountered by others, but the keyboard shortcuts to go to the next / previous mosaic do not seem to work for the mosaic tool. I've tested other keys than the ones recommended (f, d, j, k) but without any success. I've not tested the single-image tool but I can if this is useful or let me know if you have any suggestion of things i should do to help you identify the origin of the problem.
I am running the QT-tool in a dedicated python environment (cf README), on a Macbook-pro from 2018 ... (Os Ventura 13.6).
No hurry to fix this but I wanted to report it in case other users would face the same problem.
The text was updated successfully, but these errors were encountered: