Right now, if you launch Kap and move the selection window to a second screen it ignores and records the entirety of the first screen instead.
Yo @mmoutenot, thanks for the report. Will attempt to reproduce ASAP.
I believe this problem stems from not using Electron's Screen API to figure out the currently active display before recording.
Yeah that sounds about right. After testing again it seems like it might just be whatever screen you have Kap active. So the Screen API must default to that.
screen.getDisplayMatching(rect) seems like it could be useful, if not used already ;)
@mmoutenot Thanks for creating the issue! 😄
ATM, we're using Quartz's CGMainDisplayID(). TBH, I don't remember how it works, but seems that it returns the id of the display that contains the menubar.
Anyways, we definitely need to support multiple displays! I'm able to test it – I have a (_shitty_) external display lying down somewhere – so I can guarantee that we'll ship it in v1.0.0 😄
We've had a lot of issues with this recently. Priority bump? @matheuss @skllcrn @CodeTheory
@doot0 bumped to high
Most helpful comment
We've had a lot of issues with this recently. Priority bump? @matheuss @skllcrn @CodeTheory