balala wrote: ↑November 10th, 2020, 8:57 pm
Yep, it does for me as well. Didn't try out the 3D Text, just two screen savers which are not from the list of Windows 10 savers:
In neither case did it work.
But now trying out more screen savers, I got it working with more.
So, it seems the skin can be used to test the running of some screen savers, but unfortunately not all.
That's why I set the UpdateDivider option of the [MeasureProcess] to -1 when get the screen saver running. So if once the screen saver starts, the measure is no more updated, so even if the screen saver closes, the skin still shows it running. A click can restore the UpdateDivider of the measure to 1.
It did work for me in the case of your Metaballs.scr
Code: Select all
OnUpdateAction=[!Log "Screensaver is [MeasureProcess]."]
Text="Screensaver is %1."
For some reason the screen saver didn't want to be triggered automatically (i.e. only the start logo tried to appear - actually just a black box instead of it and then nothing), but it did trigger manually on the Screen Saver Settings window and its Preview button. You might want to check this too, maybe some minor up to date with the current Windows 10 versions is needed. Nice work in Delphi, by the way, I used to write several programs in it back in the day.
The only thing I did after extracting the SCR file from the ZIP was to place it in the C:\Windows\System32
folder (might work in the C:\Windows\SysWOW64
folder as well), next to the other default screen savers in Windows. Maybe this is why it didn't work for you?
The other screen saver (i.e. zzFirework.scr
) was trickier to make it work, but me knows a thing or two about debugging such unobedient pieces of software, LOL, so I figured it out eventually.
What happened is that while testing it in the Screen Saver Settings window and its Preview button worked fine, the automatic triggering used the short DOS name of ZZFIRE~1.scr
. Not sure why that happens, maybe it's older or maybe it uses a "child process" or something like that, but didn't bother to find out as my focus was simply to make it work, which I did. Didn't try to move it to the C:\Windows\SysWOW64
folder and try there, this will be up to you to test, if you like.
- initially, I thought it was because of the different file header of your SCR file (i.e. MZP instead of MZ), having tried your screen saver first, but then realized the P is just the Pascal identifier next to the MZ executable one
- here it became obvious the utility of a skin suite like mine, since the upper row of my skins (which includes the Processes skin) is set to stay always on top, helping me in identifying the actual names of the screen saver processes, since the process is usually very briefly the top one in terms of CPU usage when (repeatedly or first) running the screen saver
You do not have the required permissions to view the files attached to this post.