[Bf-committers] API: How to get a list of running scripts?

[Remigiusz Fiedler]

Dima,

> perhaps you can pass all the relevant data to the new instance of the
> script (which would continue the job), and the old one would shut down
> itself?
i use something similar already, but this is not the issue.

The problem stays (2.49 and 2.6x API): how to prevent user and other
scripts to start next instances of running scripts. As i said before,
setting a global variable as indicator of running script fails: if the
script suddenly collapses there is no way to alter the variable
automatically - the variable continues to indicate running status what
is false.


> For what reasons are you still using 2.49, by the way?
>
I like 2.49 for stability, decent system requirements
(building/developing/usage) and good performance on old hardware (like
my old portable, hehe). And for its python API.
I am prototyping a CAD system and 2.49 is more than enough for this job:
www.cad4arch.com/cadtools/
I have planed to migrate to 2.5x, but the new UI and API are quite
different and effectively still kind of restricted in compare to 2.49
version. The combination of unified API and python driven UI is a
great concept and an opportunity to create a number of easily
switchable specialized UI-s for beginners, filmmakers, animators,
game-developers, engineers, scientists, musicians... even in 2.25 or
2.49 style, but unfortunately the current implementation does not
allow it.