2009-04-22, 10:13
There are news about this.
After a little bit of code scouting, I've noticed that there must be some resource allocation/deallocation inconsistency at GUI level.
An ugly hack which prevents this bug from happening is to block the second instance of a python thread invocation based on the source code file: by doing so, keeping on clicking on a button (invoking the corresponding RunScript), only the first instance is launched and all the others get discarded.
I wonder whether this is too hard of a limitation or not: if any far more experienced user/developer could think about possible drawbacks of this approach and give me some hints I would be really glad
Thanks in advance
After a little bit of code scouting, I've noticed that there must be some resource allocation/deallocation inconsistency at GUI level.
An ugly hack which prevents this bug from happening is to block the second instance of a python thread invocation based on the source code file: by doing so, keeping on clicking on a button (invoking the corresponding RunScript), only the first instance is launched and all the others get discarded.
I wonder whether this is too hard of a limitation or not: if any far more experienced user/developer could think about possible drawbacks of this approach and give me some hints I would be really glad
Thanks in advance
