tcastudios
04-18-2007, 12:54 PM
When I try to incooperate CallCommands() in my scripts I check what CallCommand number I should use in the CommandManager.
However, some "Default" CallCommads are scripts that seems not to be "hardwired".
I.e "AddSpotLight" have a "6000000xx" number.
The thing is that thoose last xx differ at different times!
I wrote a script yesterday and it was "600000098" and to day it didn't work
since in the CommandManager ,today, says it should be "600000099"
I have stumbled into this before but thought I must be doing something strange and didn't
have time to check what was happening.
To doublechecked I see that on another machine, today the same CallCommand should be
"600000094"!
Why are -some- of the default commands "floating" scripts".
It also means that my own scripts will/could change their CallCommand numbers on each restart of the computer.
Wouldn't it be good to have at least your own scripts given a "locked" number on the same machine?
Cheers
Lennart
However, some "Default" CallCommads are scripts that seems not to be "hardwired".
I.e "AddSpotLight" have a "6000000xx" number.
The thing is that thoose last xx differ at different times!
I wrote a script yesterday and it was "600000098" and to day it didn't work
since in the CommandManager ,today, says it should be "600000099"
I have stumbled into this before but thought I must be doing something strange and didn't
have time to check what was happening.
To doublechecked I see that on another machine, today the same CallCommand should be
"600000094"!
Why are -some- of the default commands "floating" scripts".
It also means that my own scripts will/could change their CallCommand numbers on each restart of the computer.
Wouldn't it be good to have at least your own scripts given a "locked" number on the same machine?
Cheers
Lennart
