-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dual monitor #2
Comments
please, provide more information so I can try to reproduce the bug. What is your distro and your desktop environment? |
arch and bspwm |
It seems that the bug is reproducible in Awesomewm. I'll investigate it. |
Same in antergos (arch) and cinnamon desktop |
It seems to be a problem related to geometry and not dependent on specific systems (not at all). This week I plan to try to solve this with some friends as testers (so hopefully it wont end breaking previously working setups). |
I have 3 monitors, from right to left, 1366x768 - 1920x1080 - 1680x1050, the first is the desktop main monitor and the only where flameshot can capture anything. Thx. |
I think I've found a solution. I was working on it in an alternative branch and I've merged it because a friend told me it solved the issue. Could you test Flameshot from the master branch and tell me if it works? |
@lupoDharkael It works perfectly :) Thx. |
please @icf20 tell me if works for you from the master branch. |
Can confirm it works. |
ok, so I'm closing the issue now as it seems to be fixed. I plan to release a new version soon with this fix and a lot of new features! |
@lupoDharkael i am still on version flameshot 0.2.1-3 i will report back after the update hits arch(aur) |
Feature/messages and translations
I was also facing
I was also facing the issue. I made other monitor as my primary monitor and Issue resolved |
hello atm this only works on the main monitor and secondary monitor is ignored
1
flameshot gui
2 the main monitor gets the notification
3 outside main monitor the cross cursor become normal mouse pointer
The text was updated successfully, but these errors were encountered: