I just modified a script of mine to have two subroutines rather than just the single main() subroutine. The structure was:
sub main()
...
end sub
Now I've got:
sub SetAlarmFor(Nulldata)
...
end sub
sub AlarmSetFor(Nulldata)
...
end sub
The SetAlarmFor() subroutine was the "main()" subroutine before. It was a VR activated script with a VR confimation for yes or no. When I changed the sub from main to SetAlarmFor, the VR confirmation broke. It does not wait for the VR command (yes/no). It recognized "goodbye" even though the system.ClearAllVoiceCommands is issued in the script.
The strange thing is, when I name it back to "sub main()", everything works fine.
Am I crazy??
Thanks,
Doug Woolridge
P.S. I call the routine from a VR event with the following script command:
SetAlarmForPerson-DDW.txt("SetAlarmFor","")
With just "sub main()" I call it with:
SetAlarmForPerson-DDW.txt
sub main()
...
end sub
Now I've got:
sub SetAlarmFor(Nulldata)
...
end sub
sub AlarmSetFor(Nulldata)
...
end sub
The SetAlarmFor() subroutine was the "main()" subroutine before. It was a VR activated script with a VR confimation for yes or no. When I changed the sub from main to SetAlarmFor, the VR confirmation broke. It does not wait for the VR command (yes/no). It recognized "goodbye" even though the system.ClearAllVoiceCommands is issued in the script.
The strange thing is, when I name it back to "sub main()", everything works fine.
Am I crazy??
Thanks,
Doug Woolridge
P.S. I call the routine from a VR event with the following script command:
SetAlarmForPerson-DDW.txt("SetAlarmFor","")
With just "sub main()" I call it with:
SetAlarmForPerson-DDW.txt
Comment