Hello Thaluna Devs!

First off, cool tool, just bought it recently for a personal project of mine, and it works fine, but I have some inquiries regarding the requirement for windows display scaling to be 100%.

I use a widescreen monitor for my setup, and as such, an increased scaling (in my case, 125%) is basically a necessity for ease of use of my personal computer. Originally, I believed that an increased scaling would have no effect on the operation of the thaluna translation tool, because like other tools, I thought the tool used screen-capping for its window. Indeed, the lens mode works this way, and as such, I assumed the default window would have no issues as well. Yet, I found out the hard way (before checking your faq) that scaling needs to be 100% in order for the window to work, which... I find extremely odd.

Granted, I have no knowledge of how these tools work, but I assume that screen capping a part of a display captures the exact display as shown on the monitor/peripheral (almost like a camrip or recording), but seeing as this is cleary not the case for the Thaluna tool, is it not too forward of me to ask how exactly does the thaluna capture window work, and why it necessitates the scaling to be 100%? And is it possible for the tool to one-day be able to accommodate for differing monitor sizes, resolutions and scales?

Hey! Thanks for the kind words, and that's a really good question honestly.

Your reasoning makes total sense — if Lens Mode works fine with 125% scaling, it's natural to assume the capture window would too. The thing is, they actually use different capture paths internally, which is why one works and the other doesn't (yet).

The core issue isn't screen capture itself — it's how the app currently handles DPI and coordinate mapping. At 100% scaling everything lines up cleanly, but at 125% or 150% Windows and Qt can report coordinates differently (logical vs physical pixels), which causes the captured region to get offset even if the window looks perfectly fine visually.

It's something we'd like to fix, but it's not a straightforward change — the tricky part is making sure it works correctly across different scaling values, single and multi-monitor setups, mixed scaling across monitors, and different display modes. So it needs proper testing before we can ship it reliably.

For now, 100% scaling is the safest workaround for the capture window. Sorry for the inconvenience, and thanks for taking the time to explain your setup so clearly!