Being new to this forum (and relativley new to Litestep) I thought I'd carry on a fine tradition of "n00bness" by asking what will probably turn out to be a simply answered question:
Why, when I install some themes do I get the message "unititalized variable $resolutionx -440$ at line *blah blah" or something similar?
i'm quite comfertable with editing .rc files and I have located the line(s) that cause this with no problem. But what I need to know is how to FIX this. What do I change the line to?
Are you sure you have a recent Indiestep or the last .24.7 ?
Maybe $resolutionx-440$ (without the " " before the "-") should work ?
does the step.rc have that whitespace between "x" and "-"? if it is, then know that it shouldn't ;)
You can also quote the value, like so:
myBlah "$ResolutionX - 440$"
hrm.. couldn't the step parser treat $
's like "
thats what I thought...
I'll have a much more detailed look through the step.rc tonight and see if I can fix it.
It does surprise me though that a problem that seems so widespread (I've had it with a couple of theme's, and read of it on a number of occasions) doesn't seem to have a definitive solution.
Umm... WFM... spaces in var names should be no problem.
but if its enclosed in $'s and is defined as $variableX$ them trying to use $variable x$ will result in an error. Though I don't think that this is the problem.
If I remeber from my programming days (all 365 of them!) them an unitilized variable is one that is defined but not used, but I could be wrong...
Well $variable x$ won't work for the obvious reason that there is no variable called "variable x". Spaces aren't stripped from the string. But $ExistingVar + 2$ should work just fine.
An uninitialized variable is one that has not been initialized. ie, no value is supplied for it. In step.rc that means you're trying to use something without telling litestep what it is.
Make sure "resolutionx" is spelled correctly.
Make sure that - is really a - and not some funky non-ascii char.
Make sure you are using a version of litestep that supports math withing $$s. (try !alert "$1+1$" from a command box or lscp)
If all else fails, get an EXACT copy of the error message (try copy+paste) and the line it refers to.
(Just to clarify my first post)
cat $abc / dog$ ; invalid
emu $abc/dog$ ; valid
cow "$abc / dog$" ; valid
!alert "$cat$" gives me abc
. I'm not saying that litestep should handle $'s in pairs though; quotes are enough.
I have found that sometimes just using $$ is not enough, and you need to quote as well (ie. "$blah$" rather than $blah$) but I don't know why this should be.
By the way do you think this problem could be to do with me installing the theme wrong, or because the ste.rc is badly written by the author?
Isn't that simply because LS is taking the spaces in the same manner as if you had :
programfilesdir C:\program files
such that $programfilesdir$ would be c:\program
I guess it just needs the themer to think a little, or for "" to be assumed around $$ enclosed areas *shrug*
post has a good explanation of the reasons for quotes with evars
ech, maybe it really is that simple! Though could progra~1 not be used as a substitute? Seeing as it has no spaces in it but it still points to the right location. It works in DOS anways.
To be frank though, I am sick to death of this problem. Every time I try to load a new theme something is wrong. Often I can fix it no problem, but occasionally (as with this resolution buisness) I have no clue. So, I will stick with the only theme that I have found that has worked perfectly form the get go with minimal step.rc editing whcih is shell0. Thank you so much, however, for making it more obvious how the step.rc reads paths.