ThePacielloGroup/CCA-Win

New release (High-DPI, multi-monitor support)?

patrickhlauke opened this issue · 8 comments

A while ago @jun325 worked on some initial fixes for high-dpi displays https://github.com/jun325/CCA/commit/665286632c2d6b1733039f83ee83c8e4e2adca42

Is there any chance these changes can be promoted to master and a new public release be made?

seems the version in develop branch also solves multi-monitor issues as reported in #11 - so would definitely be a good thing to merge changes into master and make a new public release

nudge...anybody?

Sorry for the delay on this @jun325, @patrickhlauke. I only see one changed file in https://github.com/jun325/CCA/commit/665286632c2d6b1733039f83ee83c8e4e2adca42 (the .exe), but some of the source code must have changed too, to make this fix happen? Also there are a number of commits in Jun's develop branch after that point; do we want to merge those in too?

I could just put the .exe from Jun's commit into master here, but we should ensure that the source code in master here is up-to-date, too.

I apologize for the delay in replying.
I uploaded latest CCA(binary and source files) yesterday. 0c50a17
Could you try the high DPI support function?

Looks good - tested on Surface 3, color picker and Image > Screen overlay window all work correctly. This also fixes the eyedropper issue from #8

Only tiny visual problem (possibly just related to Surface 3's specific pixel density, which I think is fractional 1.5) is the "Show contrast results..." checkbox which is missing the top border (likely falls in between pixels on the Surface) and the slightly cramped look compared to the low-res layout (like the padding on items seems a bit smaller, in proportion, to the actual controls/text)

capture-lores

capture-hires

(sorry, accidentally closed this instead of just commenting...doh)

please try this 96984bb

tried the 64bit version. the missing top border on the checkbox is fixed, but the overall padding/spacing of some elements till feels a tiny bit cramped. not a massive problem, but would be good to address it if it's not too much trouble

capture