holmes32 bugreport has been relegated to the status of documentation: http://www.boot-land...showtopic=10625
But the issue raised there is really about the unpredicatable nature of WB script syntax. holmes32 code produces a WB error:
[Process] Set,%var%,0 If,%var%,Equal,0,Echo,"Winbuilder 080 testing coma, does it work as .script developers want?"
But I discovered we can use the Set command as a workaround to get the function working by using quotes and without resorting to #$c nonsense.
[Process] Set,%var%,0 Set,%echomessage%,"Winbuilder 080 testing coma, does it work as .script developers want?" If,%var%,Equal,0,Echo,"%echomessage%"
This is not predicatable: why work with one function but not the other? WB Russian roulette script writing. Better to get back to allowing the use of quotes -- as I thought development had agreed to anyway! Always we seem to be traversing the same ground. It's hard to make developmental progress with unpredicatability.
Please can we have some predicatability reinstated with regard to quotes. With what we agreed to, holmes32 code should be working under 080.
Thanks,
Galapo.
EDIT
Also working as a workaround:
[Process] Set,%var%,0 IniWrite,%projecttemp%\temp.ini,Section,Key,"Winbuilder 080 testing coma, does it work as .script developers want?" IniRead,%projecttemp%\temp.ini,Section,Key,%echomessage% //Set,%echomessage%,"Winbuilder 080 testing coma, does it work as .script developers want?" If,%var%,Equal,0,Echo,"%echomessage%"