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
It seems when you take an screenshot with two monitors Flameshot puts the side panel on the left side of the second screen. This is really uncomfortable as I have to move the cursor all over the two screens just to do a simple change in the tool I'm using.
Now I tried to move but It does not seem to have that capacity. So either I'm dumb and I don't get how to use it or the option is not there so if the option is there I would thanks a lot if you tell me how to do it and in case not well maybe the option could be really useful.
I don't necessary think it needs to be able to move every where. Maybe a toggle to set on which monitor it should rest could work.
Thanks for Reading!
The text was updated successfully, but these errors were encountered:
Would like to have this optione too because I'm not able to use the Sidebar. My second screen (to the left) has got a lower resolution (1080p) than the main (4K) screen. The Sidepanel on the left has got the size for the main 4K screen and is oversized so any options are out of the viewport. I'm adding an animated gif below:
Feature Description
It seems when you take an screenshot with two monitors Flameshot puts the side panel on the left side of the second screen. This is really uncomfortable as I have to move the cursor all over the two screens just to do a simple change in the tool I'm using.
Now I tried to move but It does not seem to have that capacity. So either I'm dumb and I don't get how to use it or the option is not there so if the option is there I would thanks a lot if you tell me how to do it and in case not well maybe the option could be really useful.
I don't necessary think it needs to be able to move every where. Maybe a toggle to set on which monitor it should rest could work.
Thanks for Reading!
The text was updated successfully, but these errors were encountered: