LiveCode Forums.

Hi! I have been getting very odd command line parameter responses in standalones in Windows. I have been using "-c" form for the params.

Depending on the character used I get varied yet consistent response (I tried each 3 times):
- These crash the standalone: -d,-g,-i,-v, and -w
- These return empty parameter lists (except for $0): -f,-m,-n,-p, and -s
- -u causes the process to start but no screen shows up and the process is stuck in a loop
- The rest of the alphabet is returned as appropriate in the param variable.
- It occurs whether the param is quoted or not.

Question: Are there already predefined command line options for standalones that I am conflicting with?

My entire script is :
on preOpenScript
put $0 & cr & $1 & cr into fld "fName"
end preOpenScript

All standalone settings are left at default.

By the way, the real question this is a workaround for - is there a way to send messages to stacks or standalones from a non-Rev app or script?

Thanks,
Walt

Walt,

There is an option "-ui" defined already. Perhaps, the RunRev engine searches for options (starting with a dash) and checks whether this option is "ui" in a second step. It is probably better to avoid custom options starting with a dash. Instead, you can use any command line parameter that starts with a letter or number.

Best,

Mark