I’ve been working on a major update to my Mandelbrot screensaver, a complete rewrite that brings it firmly into the world of .NET.

The project has been going pretty well, but now I’ve run into the darndest bug - one that is causing me no end of trouble.

I’m using the standard .NET application settings framework to store the settings of the screensaver.

When the screensaver is configured from the Screensaver control panel, the settings are loaded and saved correctly. I know this because the underlying user configuration file is updated and the details within the file are correct.

When the screensaver is previewed from the Screensaver control panel, the settings are loaded correctly and everything runs as it should.

But, when the screensaver is triggered by the OS, the settings are ignored and defaults are used for all of the configuration options!

Weird.

Will post when I have a solution - would love to hear of one from you!

Comments

blog comments powered by Disqus
Next Post
Preaching the wrong message  27 May 2008
Prior Post
Comfortable Clothes  24 May 2008
Related Posts
Using Constructors  27 Feb 2023
An Inconvenient API  18 Feb 2023
Method Archetypes  11 Sep 2022
A bash puzzle, solved  02 Jul 2022
A bash puzzle  25 Jun 2022
Improve your troubleshooting by aggregating errors  11 Jun 2022
Improve your troubleshooting by wrapping errors  28 May 2022
Keep your promises  14 May 2022
When are you done?  18 Apr 2022
Fixing GitHub Authentication  28 Nov 2021
Archives
May 2008
2008