Hello MBS World, I'm playing with USB volumes and WindowsDiskChangeMBS. It seems like successive fires of WindowsDiskChangeMBS may occur, not letting the previous finish with the running code.
I mean, let say a first WindowsDiskChangeMBS.DriveAdded event fires. DriveAdded event executes its code. It seems like if a second WindowsDiskChangeMBS.DriveAdded event fires before the code of the previous is finished, this first code is interrupted and DriveAdded event code starts for the second event. Am I right? If so, is it possible to avoid this behaviour (like Semaphore does with Threads code)? TIA for any help or suggestion. -- Jean-Luc Arnaud _______________________________________________ Mbsplugins_monkeybreadsoftware.info mailing list [email protected] https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
