does anyone know how to get custom evars to run when a theme is loaded? and maybe a way to close them when a new theme is loaded?
well... evars arent run, and i dont know what you mean by close them when a new theme is loaded... explain what you are thinking "evar" means
evars are only stored in memory until the next recycle. they will be unloaded/closed when the settings in memory are dumped and reloaded.
i want to run an application
*Script !exec ["$programspath$ClocX\ClocX.exe"]
it said in mzscript that i could use that but it doesnt work
didnt he refet to applications as evars in
anotherthread?
you mean
*Script start "$ProgramsPath$ClocX\ClocX.exe"
but it's better to use one.dll along with this (so as to not run ClocX again if it's already running, for example)
hmm, that didnt seem to work :( all i have to put is
*Script start "$ProgramsPath$ClocX\ClocX.exe"
???
OK this is really odd, i tried that command in antoher theme that uses a step.rc
but when i changed my theme.rc to step rc it didnt work :(
ahhh someone help :(
not to be rude or anything, but you've started a bunch of threads now, and they all smell of you not having read enough documentation. If you don't know what an evar is (Environment VARiable) or how to take advantage of it, you need to read through the LS-docs, faq's and this forum.
I mean no offence, but knowing this community, it isn't the best of ideas to start off your LS-experience by asking a bunch of questions without trying to figure out stuff yourself first. It is also common forum-etiquette to see whether there are threads that might help you without starting a new thread ;) Good luck.
Simple enough...
Just add the evar in your theme.rc like this
Calc "C:\WINDOWS\system32\calc.exe"
and then open the evar with
!exec "$calc$"
When you change themes you will have another theme.rc loaded
up and will lose calc evar from the new theme...
Now if you want the Evar to be global across all themes
place the evar in your C:\LiteStep\personal\evar.rc
But only you will have this global evar on your pc and not others if you decide to release the theme.
Hope this is what you wanted to know.
Why are you switching to step.rc to theme.rc anyway?
Stay with a theme.rc and ots2...
Its backwards compatible for ots1 and ots2, at least right now.
thanx! :) i'll try that when i get home, im at my fathers bday party right now :P um... yeah and sorry about the threads, i almost have a completely funtional mac os theme for litestep :)
hmm... that didnt work either :(
it only works with step.rc and i dont know how to switch to step.rc ":(
ok i got the programs to open but how do i use one.dll? :S
You have to add
mzScriptUseStep
if you want to place mzcript's stuff in *.rc :)
And... hmm... read the docs :)
or use systemevents.dll (/plug)