I am capturing the RQONOFF signal with my application then verifying with a dialog box that the user would really like to go to sleep. Then based on the response I put thes system to sleep.
This code is working great with CE 4.10.28. However with the new 4.20.08 Image I recieve the call back from SleepIntercept, but the screen imediatly turns off. This does not allow the user to select an option. Therefor the code never tries to put the system to sleep, making the system appear to lock-up!
There is no reason for the screen to turn off. What is going on?
Good question! Sounds like an unintended consequence of a driver change that we didn't catch in our validation testing. We'll take a look at this and let you know what we find!