Custom Skin freezes Rainmeter entirely

[InterFelix]

Hello,

I am currently working on porting TJ Markham's Win10Widgets' Spotify Widget to WebNowPlaying, so it can work with modern versions of the Spotify app. It all worked reasonably well, until I experienced some very weird behaviour. I'm working on implementing a function so that the entire skin is hidden if Spotify is not running. However, I also have a "Setting" for the skin where the user can choose if he actually wishes this behaviour or wants to see the widget no matter what. It kind of works. It definitely disappears when I close Spotify now, but I can't test if the user can switch, because Rainmeter in its entirety freezes whenever my skin is shown. When it's hidden because Spotify is closed, everything works fine. But when it's shown because Spotify is open, rainmeter and all other skins freeze. Has anyone experienced something like that? If you want, I can post my sourcecode, since I plan on releasing this skin to the public once it's finished anyways.

I am trying to fix this problem now without throwing away my added functionality, but don't really know what to do anymore.
I highly appreciate any help regarding this!

Thanks a lot!
InterFelix

[eclectic-tech]

Generally, a skin will cause a "Freeze" due to something in the way it is coded; It can be a "typo", a "continuously looping operation", etc.
So we would need to see your code to be able to help.

I realize that the suite in question uses multiple includes and "core" files, but seeing your code may give us a place to start helping.

[InterFelix]

Nevermind, I got it working. I think the freeze had to do with a missing IfTrueAction. So there was a IfCondition with no corresponding IfTrueAction or IfFalseAction.
There were some additional mistakes that might have caused this, which I didn't spot even though they were fairly obvious looking back, probably because it was way too late when I posted this yesterday.

[eclectic-tech]

Glad you found the issue.

[balala]

Nevermind, I got it working. I think the freeze had to do with a missing IfTrueAction. So there was a IfCondition with no corresponding IfTrueAction or IfFalseAction.
There were some additional mistakes that might have caused this, which I didn't spot even though they were fairly obvious looking back, probably because it was way too late when I posted this yesterday.

I doubt an IfCondition with no corresponding IfTrueAction or IfFalseAction could cause any trouble, or could freeze Rainmeter.
Rather the additional mistakes, however it depends on what those mistakes are.

[Mor3bane]

heh.

I've frozen Rainmeter for missing a semicolon, or colon in weird places. So whatever those other mistakes were, glad you nailed them.