Hey Socks the Fox,
I wonder if you could rework the plugin a bit so it acts in the Update() portion of the code, and not in the Reload() portion. The reason is that the "work-around" means that there is a one-update lag between when the wallpaper is found, and when Chameleon starts using it. During that time, I get a single, but annoying, error in the log on the "crop" options, since during that very first update, there is no image.
With the code in the Update() function it will obey Disabled=1 on the measure, which I can turn off with a FinishAction on the function that gets the wallpaper file name. Then, no error.
If you are in fact going to change the plugin to "find" the current wallpaper file, and use that before it proceeds to other things, then it's probably ok to leave it in the Reload() function.
I wonder if you could rework the plugin a bit so it acts in the Update() portion of the code, and not in the Reload() portion. The reason is that the "work-around" means that there is a one-update lag between when the wallpaper is found, and when Chameleon starts using it. During that time, I get a single, but annoying, error in the log on the "crop" options, since during that very first update, there is no image.
With the code in the Update() function it will obey Disabled=1 on the measure, which I can turn off with a FinishAction on the function that gets the wallpaper file name. Then, no error.
If you are in fact going to change the plugin to "find" the current wallpaper file, and use that before it proceeds to other things, then it's probably ok to leave it in the Reload() function.
Statistics: Posted by jsmorley — Today, 3:31 am — Replies 275 — Views 141111