Bugs & Feature Suggestions • [BUG?] Missing skin error

Hmmm, that doesn't seem right. I don't think the new "Default..." options are the culprit, but you never know.

Without something to "test", it is very difficult to find the issue. It would be best if you could post a small set of skins that demonstrate the issue, and also provide a detailed set of reproducible steps (if possible).

-Brian

After a Rainmeter crash caused by a badly written skin recently, I discovered a - probably normal, but still strange - behavior that is almost certainly related to the bug described in this thread. Steps to reproduce (I always use the context menu for all these, but it might happen if using the Manage Rainmeter window, didn't test that):
- load some skin of your choosing (e.g. Test)
- exit Rainmeter
- rename that skin's folder to something else (e.g. Test1)
- run Rainmeter
- rename back the skin folder to what it was (e.g. Test)
- do a Refresh All of your skins
- in the context menu, check the bullet indicating the loaded state of the originally named skin (e.g. Test)
Result - the skin is shown as loaded in the context menu, even though it isn't loaded anymore in the Manage Rainmeter window:Now, the difference in this reproducible scenario is that, unlike in my own from this thread (which still occasionally happens after all these years), it doesn't affect the ability to load the said skin from another one (like my tooltip skin is doing), but, given a basic attempt to do it via !ActivateConfig, you might just find out that it does (not sure about it though). Hopefully, if this reproducible case is corrected one day, maybe it will fix the problems (inability to load a half loaded skin, missing skin errors for existing skins) described in this thread too...

Statistics: Posted by Yincognito — December 29th, 2023, 5:26 pm — Replies 5 — Views 345

---