Reply to thread

Message

<blockquote data-quote="Scythe42" data-source="post: 983753" data-attributes="member: 95833">Use SystemParamertsInfo to detect if the screen saver is running (SPI_GETSCREENSAVERRUNNING). Check <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms724947(v=vs.85).aspx#Screensaver" target="_blank">http://msdn.microsoft.com/en-us/library/windows/desktop/ms724947(v=vs.85).aspx#Screensaver</a> for more details.&nbsp;Or if you want to be informed when it kicks in listen to WM_SYSCOMMAND with WParam SC_SCREENSAVE&nbsp;Or do you mean the screen blanking inside MP? This can be checked over the public method GUIGraphicsContext.BlankScreen() if it is active.&nbsp;Blanking the screen inside MP is done over:[CODE]Win32API.SendMessageA(Form.ActiveForm.Handle, WM_SYSCOMMAND, SC_MONITORPOWER, value ? MONITOR_OFF : MONITOR_ON);[/CODE]So you get a proper WM_SYSCOMMAND event anyway you can check. I would leave GUIGraphicsContext alone here and just process the relevant system messages.&nbsp;Actually the screen blanking in MP is a feature that should be removed and some handling in regards to the Win screen saver added. There are a few glitches that it kicks in when it should not. It is as simple to fix as adding a single line of code.&nbsp;MP's &quot;screen saveing&quot; will kick the bucket as it is really a not needed features that just complicates MP's setup for user and also the code.&nbsp;It brings nothing to the table in regards to MP. The power management of mainboards, CPUs and GPUs advanced that much since the release of XP that this stuff should be removed from the MP code base. That code snipped is from that time where it was OK to have such things.&nbsp;Any other event you are having trouble with? With the recent work on the Main MP message loop I am very fluent about this stuff.</blockquote>

[QUOTE="Scythe42, post: 983753, member: 95833"] Use SystemParamertsInfo to detect if the screen saver is running (SPI_GETSCREENSAVERRUNNING). Check [url]http://msdn.microsoft.com/en-us/library/windows/desktop/ms724947(v=vs.85).aspx#Screensaver[/url] for more details. Or if you want to be informed when it kicks in listen to WM_SYSCOMMAND with WParam SC_SCREENSAVE Or do you mean the screen blanking inside MP? This can be checked over the public method GUIGraphicsContext.BlankScreen() if it is active. Blanking the screen inside MP is done over: [CODE]Win32API.SendMessageA(Form.ActiveForm.Handle, WM_SYSCOMMAND, SC_MONITORPOWER, value ? MONITOR_OFF : MONITOR_ON);[/CODE]So you get a proper WM_SYSCOMMAND event anyway you can check. I would leave GUIGraphicsContext alone here and just process the relevant system messages. Actually the screen blanking in MP is a feature that should be removed and some handling in regards to the Win screen saver added. There are a few glitches that it kicks in when it should not. It is as simple to fix as adding a single line of code. MP's "screen saveing" will kick the bucket as it is really a not needed features that just complicates MP's setup for user and also the code. It brings nothing to the table in regards to MP. The power management of mainboards, CPUs and GPUs advanced that much since the release of XP that this stuff should be removed from the MP code base. That code snipped is from that time where it was OK to have such things. Any other event you are having trouble with? With the recent work on the Main MP message loop I am very fluent about this stuff. [/QUOTE]

Verification