He has a solution, surely, it is to do it from the shell. His problem is that when he goes out to the shell, it does not then play in the background.
If he calls the shell command from a separate stack, will it not then leave the original stack to just go on? So the effect will be to play in the background, and leave the user free to interact with the main stack? Of course, he'll have to handle error conditions in the second stack. This had never occurred to me till he wrote in, but it might be the solution to my printing problem. The problem is similar. You call the shell command to print, using lp, but if the printer is offline, everything freezes until it comes back online and can complete. But if the print command were to take place from a separate stack, presumably the top stack would just carry on running having passed over the shell command to the second one? Peter -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Playing-wav-sound-file-in-Linux-in-background-tp2220508p2221738.html Sent from the Revolution - User mailing list archive at Nabble.com. _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution