I don't understand what you are doing. The sysex_in_progress flag is set and cleared asynchronously by the midi input handler. If your client code is doing something that depends on this flag, it seems likely that there is a race condition. I'm not opposed to extending the API to enable a different way to structure client code if there really is a correct way to use sysex_in_progress.
-Roger Fabien Costantini wrote: > In my current code, > I must sadly rely on on PmInternal real structure which is very dirty. > Thus, I am constrained either to give the portmidi/pm_common include path to > my project > or duplicate the type definition, both alternative are just as bad. > > But the only thing I use/need in PmInternal is the sysex_in_progress flag. > ... _______________________________________________ media_api mailing list media_api@create.ucsb.edu http://lists.create.ucsb.edu/mailman/listinfo/media_api
