It is currently October 22nd, 2021, 10:48 am

[BUG] Added section variables to [Rainmeter]'s Default Settings as a joke, discovered a crash

Report bugs with the Rainmeter application and suggest features.
User avatar
Jeff
Posts: 232
Joined: September 3rd, 2018, 11:18 am

[BUG] Added section variables to [Rainmeter]'s Default Settings as a joke, discovered a crash

Post by Jeff »

I know this isn't how you're supposed to use them and that in this context what I want to do can be resolved by DefaultWindowX/Y=50%, but we were joking about horrible ways to do thing (jokes like !ToggleMeter #CurrentSection#) and all of that and I discovered that having section variables in the Default Settings actually crashes Rainmeter AND because it's not even able to load past the settings, it will always crash and not write the skin to rainmeter.ini

Take a look!

Code: Select all

[Rainmeter]
DefaultWindowX=((#WorkAreaWidth#-[week:W])/2)
DefaultWindowY=((#WorkAreaHeight#-[week:H]-[date:H]-[time:H])/2)

[String1]
Meter=String
Text=HI

[week]
Meter=String
Text=#CurrentSection#

[date]
Meter=String
Text=#CurrentSection#

[time]
Meter=String
Text=#CurrentSection#
User avatar
Brian
Developer
Posts: 2272
Joined: November 24th, 2011, 1:42 am
Location: Utah

Re: [BUG] Added section variables to [Rainmeter]'s Default Settings as a joke, discovered a crash

Post by Brian »

Thanks for the bug report. This has been fixed for the next version.

The actual problem was using the section variable parameter like :W, since it would look for the "skin" and "section" to get the value. In this case, there was no skin which caused Rainmeter to crash.

-Brian