08-21-2023, 02:59 PM
(This post was last modified: 08-21-2023, 03:06 PM by DerVVulfman.)
Time for one more
BUMP
to version 1.3
One more day has passed, but an important upgrade was required.
It came to my attention that some in the community sync their PCs with cloud services. As they connect their PCs to outside sources, these sources would require access unfettered access. And if a file was somehow protected from the cloud service, or its creation/deletion interfered with the cloud service, an issue would arise that would force a CTD (Crash to Desktop).
In order for Sharina's Screen-Saves to function, it must create .png files in which to work, and then delete them the moment their usefulness has passed. And therein lay the dilemma. It was this that cloud services would have issue. So something had to be done to resolve this issue.
It was learned that filenames that begin with certain prefixes (~$ or .~) are typically looked upon as temporary files, files that are expected to be created and later thrown aside. And these files are ignored by cloud services. And here dawned the solution.
When creating a .png file, Sharina's Screen-Saves now adds one of these prefixes to their filenames. This is an automatic process. While you (the user) may define the general name of the work file, the prefix is itself added by the system.
So now that the generated .png files are flagged as Temporary Files, cloud services will ignore and leave alone Sharina's Screen Saves and let things be.
It came to my attention that some in the community sync their PCs with cloud services. As they connect their PCs to outside sources, these sources would require access unfettered access. And if a file was somehow protected from the cloud service, or its creation/deletion interfered with the cloud service, an issue would arise that would force a CTD (Crash to Desktop).
In order for Sharina's Screen-Saves to function, it must create .png files in which to work, and then delete them the moment their usefulness has passed. And therein lay the dilemma. It was this that cloud services would have issue. So something had to be done to resolve this issue.
It was learned that filenames that begin with certain prefixes (~$ or .~) are typically looked upon as temporary files, files that are expected to be created and later thrown aside. And these files are ignored by cloud services. And here dawned the solution.
When creating a .png file, Sharina's Screen-Saves now adds one of these prefixes to their filenames. This is an automatic process. While you (the user) may define the general name of the work file, the prefix is itself added by the system.
So now that the generated .png files are flagged as Temporary Files, cloud services will ignore and leave alone Sharina's Screen Saves and let things be.
● ● ●
I should note that the issue uncovered with Temp Files would actively affect scripts that use ZLib during the creation of the Hope.gz and like files unless addressed.
But that's another system.
But that's another system.