mirror of
https://github.com/keycastr/keycastr.git
synced 2026-05-15 14:15:50 -06:00
[GH-ISSUE #36] Stopped to work when connecting a second screen #30
Labels
No labels
bug
compatibility
discussion
documentation
enhancement
help wanted
help wanted
investigation needed
pull-request
release
visualizer
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/keycastr#30
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @vichug on GitHub (Sep 27, 2015).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/36
Hi,
When i use this app on my machine it works flawlessly (osx 10.10.5). However the other day i connected a retroprojector, the screen mirroring was on and the resolution was changed, and it stopped to work. It may be related to https://github.com/keycastr/keycastr/issues/19 ; i don't know as i can't test it anymore now. I tried to quit and relaunch Keycastr, it din't solve, however i think it might have been better when i rebooted the computer.
@akitchen commented on GitHub (Oct 31, 2015):
I suspect with the resolution change the visualizer was simply offscreen. I think if you restarted keycastr it would reposition itself for the new resolution.
Could you update it and try again?
@vichug commented on GitHub (Oct 31, 2015):
Hey. Now i don't think i saw the bug again... anyway, if i open keycastr after connecting the screen, it's all good :)
i would try again with last version but i have no idea about compiling, sorry...
@akitchen commented on GitHub (Jan 18, 2016):
@vichug could you try again with the latest version from brew cask or the versions page?
@vichug commented on GitHub (Jan 18, 2016):
alas, now i don't have a setup with a second screen anymore.. i will try to test as soon as i have access to a second screne
@sdeken commented on GitHub (Sep 21, 2016):
We should avoid allowing the visualizer to be displayed outside the screen bounds. I'd like to get this corrected for 0.9.5, but I think it might take more work so I'm marking as 1.0.
@akitchen commented on GitHub (Sep 8, 2024):
I don't believe this issue is still active - please open a new issue if so