oomek
Fix issue #226
So far so good (564), but the issue is seemingly random so will keep testing (566).
Survived another wake-up. Then I locked my machine, made a coffee, unlocked, browsed the web, and then found it had frozen again... Not sure exactly when it occurred, more testing required.
The only thing I can do is also postpone window create by 2s like with audio. It is a sfml bug, all I can do are workarounds.
I've already postponed it by 2 seconds in my initial commit. The window is recreated after audio reinitialization, so honestly I don't know what else I can do here.
Locking is different to sleeping, so maybe a separate issue. Will keep testing the sleep/wake cycle.
Right, Maybe I could raise this flag also when display isn't called for several seconds?
That would also get flagged when returning from a game, since AM is not displayed at that time? This could fix a semi-related window bug:
- Occasionally when returning from a launched game the window contents get "offset"
(-8,-31)pixels - This leaves a space inside the bottom & right edges that does not get redrawn
FeWindow::display() is still called when locked unfortunately, so false lead.
Occasionally when returning from a launched game the window contents get "offset" (-8,-31) pixels
Hmm, never seen that on my machines. Is it dependent on emulator, window mode, gpu etc?
Regular Window Mode + Mame.
Sees like a resolution-change-related issue, since the -31px vert offset is the same height as the window header.
Another randomly occurring issue - will screenshot when it happens next.
I've never seen this artifact and I run AM+ in window mode 99% of the time. What is your gpu?
nVidia Quadro T1000 nothing fancy, but still shouldn't be exhibiting these issues.
Of course, Quadro... I'm 99% sure all 3 issues are caused by the Quadro driver. We've had many odd behaviours from Quadro users reported over the years, including yourself 😉