Eos update caused glitch with page if clauses
Posted: Mon Jun 01, 2020 7:49 pm
First, I'd like to say the new code editing functionality for Eos with the recent update is great.
I posted this in general forum, but it looks like this is a better place to post Eos bug reports.
Since the last Eos update, when an if block is selected on the page and you immediately select another if block, the conditional clause of one will overwrite the other. If some other element is selected in between (such as a say block), the issue does not occur. Only when selecting one if and then directly selecting some other if.
I also just happened to read the post here on the odd regular expression bug. Last week, when I was working on my console-like cheat engine for my alpha testers, I came across that very odd behavior of some page elements losing references to all variables once a regular expression was evaluated. After tinkering, I determined it had something to do with asynchronous execution and was able to get around it by adding a .1 second timer delay. But this issue is fixed now?
I posted this in general forum, but it looks like this is a better place to post Eos bug reports.
Since the last Eos update, when an if block is selected on the page and you immediately select another if block, the conditional clause of one will overwrite the other. If some other element is selected in between (such as a say block), the issue does not occur. Only when selecting one if and then directly selecting some other if.
I also just happened to read the post here on the odd regular expression bug. Last week, when I was working on my console-like cheat engine for my alpha testers, I came across that very odd behavior of some page elements losing references to all variables once a regular expression was evaluated. After tinkering, I determined it had something to do with asynchronous execution and was able to get around it by adding a .1 second timer delay. But this issue is fixed now?