SCI1.1: what in the flying hell is up with walking?

[Kawa]

Turns out all that reorganizing wasn't it -- it was disabling the messager. That's what was messing up the handsOn!

The solution?

Code: [Select]

(instance IntroScript of Script
(properties)
(method (changeState newState)
(switch (= state newState)
(case 0
(send gGame:handsOff())
(send gEgo:view(13) loop(0) setCycle(End self))
)
(case 1
(send gEgo:view(0) loop(8) cel(1) setCycle(Walk))
= seconds 4
)
(case 2
(send gTestMessager:say(0 0 0 1 self scriptNumber))
//THAT! THAT'S IT! PASSING SELF TO THE MESSAGER!
)
(case 3
//AND NOW IT'S SAFE TO HANDSON!
(send gGame:handsOn())
(send client:setScript(RoomScript))
)
)
)
)holycrap

Edit: copied rm110.sc into the backup I made that has all the neat UI edits and such and rebuilt. Can I have a "blammo"?

[troflip]

We'll need good documentation for the messeger::say method.

It looks like the say method returns immediately, meaning the subsequent code is executed right away. So if you want to wait until the message has disappeared or been dismissed, you need to make a new state and pass self in order to get cued to change to the next state.

The messager (actually the Talker) messes with enabling/disabling the icon bar when it's shown/hidden, so that probably conflicted with you changing handson while it was up.

[Kawa]

It looks like the say method returns immediately, meaning the subsequent code is executed right away. So if you want to wait until the message has disappeared or been dismissed, you need to make a new state and pass self in order to get cued to change to the next state.

The messager (actually the Talker) messes with enabling/disabling the icon bar when it's shown/hidden, so that probably conflicted with you changing handson while it was up.

In the wise words of Krim Steinbelt: Exactly!