Another thing that causes me nautia... I''m writting a screensaver. I know that windows run it, and use command line arguments to control it. The problem is that MY windows sends me the /p xxxxxxparameter, when i press configure (from display->popup)! When i use the preview button, i get the /s parameter! What is going on??? What do i know wrong? What do i do wrong (besides taking tasks for Windows platform )? Any tips/ideas? ... LEMMINGS ... LEMMINGS ... LEMMINGS ... LEM..... SpLaSh!... Is it what we look like on the eyes of destiny or God? Are we LeMmIngS or WhAt!?

The /s parameter tells the screen saver to run as normal,

The /c parameter tells the screen saver to show it''s configuration dialog, with the currently active window as the parent (to stop the user from clicking on the "Configure" button multiple times and running multiple copies of your config dialog)

The /p xxx parameter is meant for showing a preview of the screensaver in the small preview window. The "xxx" is how you identify the window you should draw the preview into. Having never actually made a screen saver myself, I don''t know how it identifies the window. My suggestion is to check MSDN. I would guess though, that if you get a /p parameter, it''s not entirely unacceptable to just quit and not display a preview.

If no parameters are given, you should run the config dialog with no parent window.

---

War Worlds - A 3D Real-Time Strategy game in development.