🚀 go-pugleaf

Hello, Here is a thread example:

DWORD CALLBACK ThreadFunc(void* P)
{
 HDC DC=GetDC(Form1->Handle);

PlaySound("c:\\Key.wav",NULL,SND_FILENAME);
ReleaseDC(Form1->Handle, DC);

 return 0;
}

void __fastcall TForm1::PlaySoundInThread()    file://play sound in edit
boxes
{
  DWORD ThreadID;

HANDLE hthread = CreateThread(0,0,ThreadFunc, 0,0, &ThreadID);
}


So to play the sound in the thread on a button click just use this line
instead of playsound(),

PlaySoundInThread();

Goodluck.

Mike <someone@somewhere.com> wrote in message
news:3B8632A5.5F1864A9@somewhere.com...
> Hi!
>
> So, I read help about threads and WAVE playback and I found out
> that for me it would be the best to use "callback function". And, so,
> I have some questions about it.
>
> I have an thread which is created when I would like to playback
> WAVE file (and if I would like to use "thread callback" there would
> be yet another one, wouldn't be?), but I need very accurate playback
> (without dropping any samples and that it would be as real-time
> as it is possible (so little buffers, because WAVE files is generated
> in real time)), so "callback function" is what I need.
>
> How can I declare it (so that I can than with an argument
> (DWORD)WaveProc give waveOutOpen function's location (so that it
> would know what to call))? I tryed this
>
> void CALLBACK WaveProc(HWND hWnd, UINT uMsg, WPARAM wParam, LPARAM
> lParam) {
> ... I left code for function the same
>
> but I get illegal operations
>
> Maybe I should make it thread-function (how?)?
>
> And what's the priority of this function (it's default or it is thread's
> priority)?
>
>
> Mike
>
>