Re: Win32Lib: PlaySound/setVisible solution
- Posted by Dan Moyer <DanMoyer at PRODIGY.NET> Nov 05, 1999
- 550 views
Brian, Not only did I find your example "useful", but it is now successfully incorperated into my math flash card app, works REALLY WONDERFULY, allows the "interruptiblity" I liked so much about playSound async, & I'm about 99% finished with it!! Wow! Now all I got to do is finish the last 1% & try to clean up the commenting so it could make sense & potentially be useful to others, & I'll send it to RDS. I do still need to find out if David has a fix for the "modal windows" problem I found before I can let my niece & nephew use it, though, 'cause that can make it hang up. I'm really grateful to you not only for the code itself, but for your observation that my initial alterations of it were anything but an "improvement", which prompted me to go back & do what I should have done in the first place & run your original code sans my "improvement". My only excuse is that I didn't really understand it very well, & tried to modify it into something that I understood slightly better. Getting your timer-based "play multiple waves" to work in my app wasn't as easy as I had hoped, but that was mostly my programming ignorance hindering me, & the fact that I had timers running in it already, which I had to make work together correctly with yours. But I did it, & I'm much MUCH more pleased with it now than when I was using playSound sync mode. I wouldn't ever have thought of that approach myself. So thanks a LOT!! re C_SHORT: yeah, I do have DLL.E in my include directory (& it does define C_SHORT), & 0.42e Win32Lib is there too, and no earlier version is in the directory with my app, so I don't know why euphoria hiccupped on it, but as long as LONG works ok, it's ok by me. Thanks again! Dan Moyer On Wed, 3 Nov 1999 21:09:22 -0500, Brian Broker <bkb at CNW.COM> wrote: >On Wed, 3 Nov 1999 20:36:06 -0500, Dan Moyer <DanMoyer at PRODIGY.NET> wrote: > >>I did change C_SHORT to C_LONG in the re- >>definition of playSound when euphoria said C_SHORT wasn't defined, but I >>really don't have any idea whether that is ok or not. (In other words, I >>really don't know what I'm doing.) > >Well, a C_LONG is the same as a C_INT and that should work fine. Bernie >mentioned that a boolean value is a C_SHORT. These constants essentially >define how data is stored in a way that C understands. A Short integer is >16-bits while a Long integer is 32-bits. So defining the return value as a >Long will work, it's just overkill. (Of course, only one bit is required to >determine True or False so using a Short integer is also overkill.) > >These values should be defined in DLL.E in your INCLUDE directory (dll.e is >included by win32lib.ew). What version of Euphoria are you using? Perhaps >an older version of DLL.E did not define C_SHORT? > >Either way, as long as it works... I'm glad to hear that you might find my >example useful after all! > >-- Brian