Description
Changing the scaling factor for the display when the app is in system tray will introduce inconsistent recording areas and positions.
Reproducible steps
- start the app
- record the screen, it records properly
- change the scaling on the display settings
- now record after invoking again . (record a sanely large area) it should mess up the area and the positions.
Possible Solution
scale_factor can be a dynamic var or we could shift the spawn to record scale_factor only on invoking cmd shift 2 (or ctrl shift 2)
Notes
- I've have only tested this in dev build , not in production.
- This behavior will probably go away when we eventually roll out multi monitor support, so i think we should look into this after that.
Description
Changing the scaling factor for the display when the app is in system tray will introduce inconsistent recording areas and positions.
Reproducible steps
Possible Solution
scale_factor can be a dynamic var or we could shift the spawn to record scale_factor only on invoking cmd shift 2 (or ctrl shift 2)
Notes