-
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
External screens not available (until restart of Flameshot) #3505
Comments
Second this on Windows. Flameshot snapshots your multi-screen configuration on startup and then keeps that regardless of plugging or unplugging and moving to different setups with the device. Would love a fix for this. |
seems the problem could be fixed by using: (but I'm not a contributor atm. and don't have time to read into the code. just this trigger doesn't occur in the code anywhere , although it seems it should) |
This comment was marked as duplicate.
This comment was marked as duplicate.
I can confirm that restarting flameshot on OSX fixed the issue for me. EDIT: fixed it temporarily as @Saibamen pointed out. |
This is a workaround, not fixing |
I'm trying today to apply the advice from #3505 (comment) and see if that works in general, if it does I'll link my pull request here. First impressions are good, but I'm not fluent in C++ or QT so I can't promise anything. |
…niitalize Flameshot when the display configuration changes
…niitalize Flameshot when the display configuration changes
PR here but I don't know if it really really helps. You can try cloning my branch and building with
|
@leehambley Tried it, it does detect the external monitor (even after unplugging and plugging again) 👍 However, it introduces a couple of regressions:
Tested on MacBook Air M2 with 1 external monitor. |
Came here to say that I love Flameshot but this has been bugging me for a while now. The most annoying part is when I right click on the taskbar icon to quit flameshot but I can only see the first menu item because the rest of it is off the screen. Would love to see some progress here! |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Yes, the development have slowed down. Partly since our main dev stepped down, and partly because we received death threats (yes, genuinely) and nasty messages from users. People don't [want to] understand that we are all volunteers in this project, we don't accept donations nor we we get money working on this. We have asked users to put bounty on the issues they need to solve, this way their money directly translates to actual tangible improvement, but it also attracts people to contribute to the project. So far, the nasty comments are still coming in, and not much bounty have been put on issues to attract new developers. So we develop the project with the pace that we can without getting burn-out. I hope this make sense. |
Flameshot Version
v12.1.0 (96c2c82)
Installation Type
brew install --cask flameshot
Operating System type and version
Soonoma 14.3.1
Description
Flameshot area doesn't extend to external screens when plugging them in.
So taking a screenshot or "selection" only involves the main display of the M2 Mac.
Tried to reinstalled etc. but the problem still occures (this problem exists since a few months)
Current workaround found: close flameshot and reopen -> but this is really annoying over time
Steps to reproduce
Screenshots or screen recordings
No response
System Information
The text was updated successfully, but these errors were encountered: