MN_MrNoob
There seems to be a misunderstanding between the game/app pause feature and screen freezing. If you haven’t specifically configured autopause in Lookupper, what you’re seeing as a pause is actually screen freezing — and it’s there for a particular reason.
A while ago, in versions before 1.6 (I believe), Lookupper didn’t have screen freezing. Instead, it tried to open a popup directly on top of the actual words on the screen. The problem with that approach was that if the text changed, the OCR performed when you first pressed the hotkey would become completely miss in a constantly changing situation. It was awful — you’d see one word but get the definition of another.
That’s why I implemented screen freezing. It uses a very simple technique: it takes a screenshot of your screen and displays it on top, keeping it there until you’re finished. Everything looks smooth now. Yes, the background app keeps running behind, but we no longer rely on it. This prevents frustrating situations where Lookupper shows information about words that are no longer on the screen.
For example, without screen freezing, imagine you’re watching a YouTube video with subtitles. You press Alt+Q, Lookupper highlights the subtitles that were on screen at the exact moment you pressed the hotkey. Then the video continues playing — new subtitles appear — but Lookupper keeps showing the highlights for the old words. This drove many users crazy, including me.
I’m still considering how to combine both worlds: how to remove screen freezing while making sure Lookupper never highlights words that have already disappeared from the screen.
If you could describe the specific problems you’re facing with the screen freeze, I could come up with a better solution. Could you please share more details about which app or game you’re using Lookupper with? (That way I can try it myself and better understand your frustration.)
