PureBasic Forums - English

We have PlaySound(), and we can stop playback immediately with StopSound(). Am I right to think that the Sound Lib runs in a separate thread?

The reason I ask is that I feel the Thread Library is missing a function: Stop Thread. In some situations, stopping a thread that has a repeat loop is too slow if reliant on checking for a global var change, as recommended in the help. The alternative in that case is Kill Thread, which is too abrupt because the thread cannot run it's clean-up. So, a Stop Thread Function would in an ideal world deliver the best of both - stop quickly but complete it's current cycle.

Am I as mad as the mirror suggests?

Sometimes KillThread is fine and you don't need anything else but in other cases where your thread is working with objects like images and gadgets, an abrupt killing of the thread could cause a crash (say a StartDrawing was open and the thread was killed before you got to StopDrawing would be one example). In cases like this, I've had good results with this approach: I'm not sure if the compiler could provide a catch-all solution for every case or not, I just don't know. Maybe it's possible.

Hi Netmaestro

That is the method I normally use, as recommended in the help....... but sometimes it isn't good enough.

Why do you call it 'too slow' ?

...because the global var is changed elsewhere in the app and subject to any kind of potential delay - a delay that probably helped you to decide to create a thread for the most critical part of the process in the first place.