08-26-2015, 09:57 AM
Thread get and Thread remove work as documented. These are not the best tools for determining if a program is running or asking it to quit.
The "TeamID" for a running yab script will change depending on how the program was launched making it less useful for programming a solid app that uses this function. Examole:
Launch Clock.yab from a Terminal and the TeamID is "yab ./Clock.yab"
Launch it from Tracker and the TeamID changes to "yab /boot/home/yab_work/Programs/Examples/Clock.yab"
Launch it from within yab-IDE and it is even less obvious as the "yab" is replaced by "/boot/home/config/non-packaged/bin/yab" or "/boot/system/bin/yab" or "/boot/home/config/bin/yab" depending on how yab is installed. in any case, the path becomes too long to identify the Clock.yab by TeamID as only the first 64 bytes of the path are used.
ThreadID is the most useful, but only if the program is compiled using the BuildFactory. Yab scriptsis become simply one or more threads of the yab team.
The "TeamID" for a running yab script will change depending on how the program was launched making it less useful for programming a solid app that uses this function. Examole:
Launch Clock.yab from a Terminal and the TeamID is "yab ./Clock.yab"
Launch it from Tracker and the TeamID changes to "yab /boot/home/yab_work/Programs/Examples/Clock.yab"
Launch it from within yab-IDE and it is even less obvious as the "yab" is replaced by "/boot/home/config/non-packaged/bin/yab" or "/boot/system/bin/yab" or "/boot/home/config/bin/yab" depending on how yab is installed. in any case, the path becomes too long to identify the Clock.yab by TeamID as only the first 64 bytes of the path are used.
ThreadID is the most useful, but only if the program is compiled using the BuildFactory. Yab scriptsis become simply one or more threads of the yab team.
