I keep getting the following error in RR (see below). The only way out of it is to quit the app. I'm "clicking around" and trying different scripts from tutorials, etc. So, I'm not sure if something I'm doing is causing this (well, duh, that has to be the case). However, I'm certainly not doing anything related to backgroundColor, so, the presence of this error is all the more confusing.
While it's not happening ALL of the time, it's occurred at least a few times over the last couple of days. No, I can't create the "steps to reproduce" as I don't know what is triggering this. However, the last time it occurred I believe I was experimenting with insert a "wait 3 seconds" command just before some other command and things seem to lock up on me and somehow I got led to this.
----------------
executing at 4:04:52 PM
Type Function: error in function handler
Object Editor
Line set the backgroundColor of field "Script" of me to sePrefGet("editor,backgroundColor")
Hint sePrefGet
confusing error in function handler
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Hi Bill,
It appears that an increasingly large number of people is encountering this and similar problems. It has been reported here and I'm pretty sure RunRev Ltd will try to solve the problem in the next release.
Please, add your own comments to the bug report.
Best regards,
Mark
It appears that an increasingly large number of people is encountering this and similar problems. It has been reported here and I'm pretty sure RunRev Ltd will try to solve the problem in the next release.
Please, add your own comments to the bug report.
Best regards,
Mark
The biggest LiveCode group on Facebook: https://www.facebook.com/groups/livecode.developers
The book "Programming LiveCode for the Real Beginner"! Get it here! http://tinyurl.com/book-livecode
The book "Programming LiveCode for the Real Beginner"! Get it here! http://tinyurl.com/book-livecode
Okay I just added the report to the bug db.
Mark wrote:Hi Bill,
It appears that an increasingly large number of people is encountering this and similar problems. It has been reported here and I'm pretty sure RunRev Ltd will try to solve the problem in the next release.
Please, add your own comments to the bug report.
Best regards,
Mark