🚀 go-pugleaf

Hi all, sorry to post again about this but it is a TOTAL MISTERY to me.

I posted a few days ago regarding intercepting the WM_SYSCOMMAND in order to
stop the Windows Screen Saver kicking in.  I had defined a message
processing function, thus:

void __fastcall TMainForm::ProcessMessage(tagMSG &msg, bool &Handled)
{
   // Message Processing / Handling switch.
   switch (msg.message)
   {
      case WM_SYSCOMMAND         :  if (msg.wParam == SC_SCREENSAVE)
                                    {
                                       Handled = true;
                                       //handled =
Config->getGlobalConBit(DISABLE_WIN_SCREEN_SAVER);
                                    }
                                    break;
      default                    :  Handled = false;
                                    break;
   }
}

- now, lone behold, when I run the application, in or out of the IDE, the
B*%$T^�D screen saver still kicks in.  Remy said that there shouldn't be any
problems with the code so I set of hunting, throught all 14 lines to see
what the problems is.  Couldn;t find anything so I created a new application
and this time I dropped on a TApplicationEvents vcl, coded the OnMessage
event thus:

void __fastcall TForm1::ApplicationEvents1Message(tagMSG &Msg,
      bool &Handled)
{
   if ((Msg.message == WM_SYSCOMMAND)&&(Msg.wParam == SC_SCREENSAVE))
   {
      Handled = true;
   }
}

- and guess what - the screen saver still kicks in.  In both cases the
messages are being recieved and processed (and I assume handled) because
I've inserted code to change the main forms caption just after the handled =
true point and it changes.

I almost feel embrased posted because it is such a simple thing and I can't
for the life of me workout why it's not working.  It worked fine the last
time I coded it (another PC and Builder 5).  Any suggestions would be great.
This is really doing my head in.

Living in hope :-)

Mike C