You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed this when experimenting with the new interruption controls and switching quickly between a game and preferences window.
If I open / switch to the preferences but switch back to a game window before it starts describing the current preferences, it will describe them anyway and interrupt the game while doing so. Changing the new VO interruption controls doesn't seem to effect this behavior. The game switched from will ocasionally also interject when switching to the prefrrences window, though this is much less consistant and I couldn't reproduce it just now.
The text was updated successfully, but these errors were encountered:
I made some more fixes to make extra sure that VoiceOver will not speak text from a game in the background, which might help with the last part.
The main problem seems like an Apple bug to me, though. I'm not doing anything custom with VoiceOver in the preferences, it is all standard controls being described in the default way, so I don't know if there is anything I can do about it.
Okay, I found the same problem in another Cocoa app I use. It was just similar enough to the problem with game windows overlapping that I assumed it was Spatterlight specific. The issue regarding the game windows does seem to finally be gone!
I noticed this when experimenting with the new interruption controls and switching quickly between a game and preferences window.
If I open / switch to the preferences but switch back to a game window before it starts describing the current preferences, it will describe them anyway and interrupt the game while doing so. Changing the new VO interruption controls doesn't seem to effect this behavior. The game switched from will ocasionally also interject when switching to the prefrrences window, though this is much less consistant and I couldn't reproduce it just now.
The text was updated successfully, but these errors were encountered: