I think I found a minor bug in the original DeNGVaT code. It's probably fixed in the enwer version (I'm sticking weith the old version for various reasons) but thought I'd mention it for the record.
Code: ags
result: the second line ERASES the content of 'cutscene_waiting'
workaround: this only happens if 'rightClickedObject' has not been defined. Adding Global.Sets("rightClickedObject",""); at an earlier stage fixes it.
EDIT:
It seems I spoke too soon. On further examination, it appears that, in some circumstances, TWO globals can be stored with the same name. So when you then search for that global, you may access the wrong value. Any suggestions would be much appreciated!
LATER EDIT:
It's possible that the previous problem was caused by a line in the 'find' function. If anyone's interested I'll post more details.
String test = Global.Gets("cutscene_waiting"); Display("1 waiting:'%s'",test);
String what = Global.Gets("rightClickedObject");
String test2 = Global.Gets("cutscene_waiting"); Display("2 waiting:'%s'",test2);
result: the second line ERASES the content of 'cutscene_waiting'
workaround: this only happens if 'rightClickedObject' has not been defined. Adding Global.Sets("rightClickedObject",""); at an earlier stage fixes it.
EDIT:
It seems I spoke too soon. On further examination, it appears that, in some circumstances, TWO globals can be stored with the same name. So when you then search for that global, you may access the wrong value. Any suggestions would be much appreciated!
LATER EDIT:
It's possible that the previous problem was caused by a line in the 'find' function. If anyone's interested I'll post more details.