Addons or other executables, files, running in the background when installing a .RMSKIN installation file causes a write conflict. Allowing Rainmeter time to properly shut itself down prior to installing a new skin would allow Authors to use OnCloseAction to implement controls to exit conflicting processes that otherwise prevent the .RMSKIN from completing an installation.
eg. I have an executable made with AHK that acts as a background processes to help facilitate certain tasks/commands in Rainmeter. This executable exists inside the @Resources\Scripts location of my skin. An .RMSKIN cannot install an update to this skin unless that executable is closed first. There is no existing control to prevent this.
Allowing Rainmeter to close (soft close, not kill task) prior to proceeding with the .RMSKIN installation would mitigate this problem.
Additionally, when this error does occur, the error message box is vague and doesn't provide any instruction to the user. It just says "Failed to backup..." etc. Why not change the message to "Installation failed. Please terminate any running processes that may exist in the installation directory and try again".
eg. I have an executable made with AHK that acts as a background processes to help facilitate certain tasks/commands in Rainmeter. This executable exists inside the @Resources\Scripts location of my skin. An .RMSKIN cannot install an update to this skin unless that executable is closed first. There is no existing control to prevent this.
Allowing Rainmeter to close (soft close, not kill task) prior to proceeding with the .RMSKIN installation would mitigate this problem.
Additionally, when this error does occur, the error message box is vague and doesn't provide any instruction to the user. It just says "Failed to backup..." etc. Why not change the message to "Installation failed. Please terminate any running processes that may exist in the installation directory and try again".
Statistics: Posted by Cariboudjan — Yesterday, 7:53 pm — Replies 1 — Views 53