This posting is older than 6 months and can contain outdated information.
Thanks for your detailed reply.
This is the new default behaviour of Lion and not caused, controllable or influenced by Remote Buddy. It has already annoyed me ever since I started using Lion Pre-Releases. (For reference, here's a random forum post on this topic from Apple's Support Communities: https://discussions.apple.com/thread/3193005).
Ok so you are saying that the new "feature" in Lion to only wake the monitor on click or keystroke is what caused the issue in Remote Buddy. Is everyone experiencing this problem then? Including people with Apple IR receivers? And users that don't use Remote Buddy, but just the apple remote with front row?
The only alternative available right now would be for Remote Buddy to send a keystroke - which it can't actually do, because, depending on where you are, this might trigger an action in an application.
Actually, if you can detect when the monitor is asleep then sending a keystroke does not affect the foreground application. I regularly wake my monitor by hitting random keys and the first keystroke is always suppressed, the subsequent ones even before the monitor is fully awake are not though. Another option might be to click on a safe location on the screen like the Apple menu and then a second time to make it go away. It would probably happen faster than the monitor could wake so the user would never see it.
Last edited: 22.07.2011 11:30:34
