LeonaMorro
commented
9 years ago SCHMO(E) Syntax:
I try to make a short table out of the currently possible combinations:
| CMD | valuation |
|---|---|
SCHMO(E)|seat# |
useless |
SCHMO(E)|seat#|animation |
can be usefull in some cases |
SCHMO(E)|seat#|animation|position |
can be usefull in some more cases |
SCHMO(E)|seat#|animation|position|rotation |
usefull but not always* |
SCHMO(E)|seat#|animation|position|rotation|facial |
very usefull but not always** |
SCHMO(E)|seat#|animation|position|rotation|facial|seatName |
always good |
(* you can expand your above example and say: If I set a facial in one SCHMO(E) command it stays if it isn't removed in other SCHMO(E) commands .. ) (\ you can expand your above example and say: If I set a seat name in one SCHMO(E) command it stays if it isn't removed in other SCHMO(E) commands .. )
My goal was to give the user the maximum of freedom in creating the command (even if he/she has to think about what he is doing).
I think your goal is to take the user by the hand and eliminate the need of thinking about what he/she is doing (Which may result in less support questions).
I think both are good goals.
Restricting the command to only work with a certain number of parameters would also require an additional line of code to the script (Thats why I didn't disable the SCHMO(E)|seat# so it is valid, legal and useless but also does no harm). The syntax description SCHMO|seat#[|animation[|<0,0,0>[|<0,0,0>[|facial[|seat name]]]]] currently reflects the code, not the usefulness.
After all that said I could think of a third way which may obtain your approval:
We could change only the documentation to:
Syntax: SCHMO|seat#[|animation[|position[|rotation[|facial[|seat name]]]]]
Recommended use: SCHMO|seat#|animation|position|rotation[|facial[|seat name]]
or if we also like to respect * and **:
Recommended use: SCHMO|seat#|animation|position|rotation|facial|seat name
HowardBaxton
SCHMO|seat#[|animation[|<0,0,0>[|<0,0,0>[|facial[|seat name]]]]]This syntax suggests that the only required items are SCHMO and seat#, yet a line below makes no sense to use:
SCHMO|1Next I thought well maybe a line such as
SCHMO|1||<2, 0, 1>would make sense. However this line gives an error "Could not find animation: ". Thus I believe the syntax requires the animation and should not be one of the optional items. To make animation optional, the code line should look something more like this:if(index==2 && llList2String(params, 2) {. Now the above NC line works. This could be done for all these items.Next I tried something like this:
SCHMO|1|otherAnimation. I was thinking this made sense because I didn't want to change any of the other items from the slots list. This does work until I needed to make another SCHMO line that did require a position change. I added a second NC but after switching to this new pose set and then back to the one above, the position was wrong. This leads me to also believe that position and rotation also cannot be optional.Next I tried making all SCHMO(E) pose sets within BTN cards. This appears to work well until some contents of the build change. The changed event checks if our last card name exists and runs DOPOSE on our BTN NC. The slots list then becomes empty for some reason and no one can sit without running a pose set with ANIM lines. I thought to try tracking this down in the scripts but will be difficult when we start out running DOPOSE on a NC that should be DOACTION. The better fix for this is to be sure to do SCHMO(E) in SET type NC's.
My recommendations are as follows:
SCHMO|seat#|animation|<0,0,0>|<0,0,0>[|facial[|seat name]]SCHMOE|seat#|animation|<0,0,0>|<0,0,0>[|facial[|seat name]]