Threading library for optimising compiler

[agraham]

The introduction of the true compiler for Basic4PPC opens up some avenues previously closed. One of these is the ability to write threads in Basic4PPC code rather than only being able to do this in a library.

Some/most of you will know that a thread is a separate flow of program execution. Basic4PPC normally has only one thread, the GUI (Graphical User Interface) thread that, not surprisingly, handles the user interface (and everything else). Using this library you can create additional threads that operate (apparently) in parallel alongside each other and the GUI thread.

Threads can be useful to keep the user interface alive while performing a long sequence of computations. For instance my Flite speech dll for the device runs on the GUI thread and while it is speaking you can't do anything else. Included is an example of running it on a thread so you can set it off and leave it to run and carry on user interaction. You need FliteDevice.dll and fliteDLL.dll in the app folder on the device.
Speech library for the DEVICE!
Compile ThreadTestDevice.sbp optimised for device with FliteDevice.dll and Threading.dll in the desktop app folder and transfer the resulting exe and Threading.dll to the device app folder.

The library protects itself if it finds itself running in a legacy mode so hopefully you can't crash your app whilst playing! I'll produce a help with more info later. However there is a load of comment in the ThreadTest app to hopefully give you enough information to try it out - should you dare!

EDIT :-I've updated demo source as per dzt comment below. Also I just noticed a minor issue in my workarounds to issue warnings when running in legacy mode (where it doesn't work anyway). I don't quite understand the problem at the moment but it doesn't really matter as it is cosmetic really. Just shows you can't do enough testing before release

EDIT :- Update to version 1.1 to warn politely (as always intended) rather than throw an error when any of the RunLocked calls were used in legacy mode.

EDIT : - Updated to 1.2 with Process object added.

EDIT : - Updated to 1.3 with support for module name prefixes for the thread Sub. Help and source included. Demo sources are in 6.50 format but the library is compatible with all Basic4ppc 6.xx releases.

[dzt]

Excelent!!!

A lot of knowledge is hidden here. And of course a lot of work

PS.
You should immediately turn "Check for unassigned / unused variables" on.
Try to run ThreadTest.sbp in debug mode

[agraham]

Originally Posted by dzt

You should immediately turn "Check for unassigned / unused variables" on

Thanks dzt. I keep doing that - turning it off for testing then forgetting to turn it back on! Zip modified.

[agraham]

Help now added to the original post. As well as documenting the library it includes a brief introduction to threads and processes.

[agraham]

Library version 1.2 and updated help posted to original post. This version changes the name of the "Threader "object to "Thread" as I didn't like the original name and it's my library and I can do what want with it Otherwise there are no changes to the Thread object.

Added is a Process object which provides the facility that several people have asked for in the past. This is the ability to start a program (process) and know when it has finished. The Shell statement in B4PPC starts a program (process) but that is all. The Process object here can start a program, provide an Event when it terminates and can forcibly terminate it if required.

[dzt]

Originally Posted by agraham

...This version changes the name of the "Threader "object to "Thread" as I didn't like the original name and it's my library and I can do what want with it ...

I feel the need to say again how useful is this library, as there are many b4ppc functions taking long time to finish (FTP, Image processing etc.) and until then it is not so elegant to have the UI frozen.

I also should say that I love Process object.

[Cableguy]

I'm about to use this lib for the first time, so before i do i need to ask just one thing...
I need to thread a timer...
is this thread fired as a single sub? (timer1_tick)???

[agraham]

Originally Posted by Cableguy

I need to thread a timer...

Can I ask why? Actually this is not possible due to the nature of what a timer is. Tell me what you need and perhaps we can see how to achieve it.

[Cableguy]

I am writing an "alert" progam, in wich the user will enter a series of data including a date field...
in the mean time the program ( i have thought of an "external"program...), will, twice a day, as setted by the user, check if the date entered above matches the Today date, and if true, pop-up an Alert....But it must not halt the execution...
So what the best way to go?

[agraham]

Two possibilities spring to mind.

For both possibilities I would suggest using a timer with a fairly long interval to check whether it is the right time to start one of these checks then :-

a) Start another timer or reset the original timer's interval to be shorter, say 500mS or so. Do the data checks in the timer code but structure the code so that it, for example, checks one set of data, saves where it has got to in one or more global variables, then exits the timer picking up the data to check the next set in the next timer tick, saving and exiting again, and so on till complete.

b) Use the timer code to start a separate thread that does the checking in a long code loop without returning. If you want to display the alerts from within that code you would need to use a timer event as shown in the sample app. Alternatively you could build some global variables with the alert data and then set a global flag when the thread completes that the timer could check for and then display whatever is needed.