Yep, I knew that one. But we don't want to disable the visibility of an object (button) that still needs to be animated, do we? Or its "physical" properties for that matter, which would be closer to the mark. I think if you disable the activator through Python you disable just that, its clickability.
Edit: Ok, scratch that last part. It looks like Python also disables the physics. So I am going to try something this.
- Code: Select all
- type: enablemsg
params:
receivers:
- scnobj:<clickable>
cmds:
- physical
- disable
waiton: -1
#do other responder stuff
- type: enablemsg
params:
receivers:
- scnobj:<clickable>
cmds:
- physical
- enable
waiton: -1
Edit 2: Status - failure. Physics are not enabled when the Cyan Python script fast forwards the animation state at link in, even though it is the last step in the responder sequence. So the button is no longer a clickable.
Edit 3: I tried to directly reference the logicmod but that did not seem to have any effect.
- Code: Select all
- type: enablemsg
params:
receivers:
- logicmod:$<modifier tag>
cmds:
- physical
- disable
waiton: -1
#do other responder stuff
- type: enablemsg
params:
receivers:
- logicmod:$<modifier tag>
cmds:
- physical
- enable
waiton: -1
The button was clickable all the time as in the original script. Maybe that was because the logicmod does not listen to "- physical - disable". But more likely the enable message at the end should wait for a callback from the last action in the sequence. Callbacks however are currently only implemented for oneshotmods. So I am giving up for now.