bcw@rti.rti.org (Bruce Wright) (08/02/90)
I'm having a problem using the SetVoiceAccent call under Windows V3.0. I have a program I wrote originally in Microsoft C under Windows V2.1 which uses the SetVoiceAccent call to adjust the tempo and mode (LEGATO, NORMAL, or STACCATO) for playing tunes, and under Windows V2.1 it works just fine. But on Windows V3.0 the call never seems to take effect - as if it is ignored. This is possible if one of the parameters is out of range, but I am checking the return value from the function and it thinks that the function completed successfully. Interestingly, if I deliberately set an illegal value into one of the parameters to the SetVoiceAccent call, I get the appropriate invalid parameter return code when I run the program under Windows V2.1 but not when I run it under Windows V3.0 - it always returns success!! I've also tried it on various machines with similar results, so it isn't something strange about just one machine. The program does go on to play the tune more-or-less correctly (except that the accent is wrong - it always uses the default tempo and the default mode rather than the ones the user has selected). Nothing else in the program seems to have been adversely affected by Windows V3.0, nor in any other program I've written for Windows (except of course for needing to be marked as capable of running under protected mode), though that program is the only one that uses the SetVoiceAccent call. Microsoft user support does not seem to know about any such bug, but wants $800 for a subscription to Microsoft Online if I want to ask the SDK support people if such a bug exists. Does anyone know if such a problem exists under Windows 3.0 and if there is a workaround or an update available? My apologies if this topic has come up before, I've just back after not reading the netnews for some time because of lack of time and being out of town. Thanks for any info - Bruce C. Wright