So in my continuing battle between the forces of reason and BITS I have run up against a wall in trying to talk to my winamp player.

I have gotten much to work but the following has got me stumped on how to do this it STRUCT me that there must be some help on this board (pleasepleaseplease

/*

Some API calls tend to require that you send data via WM_COPYDATA instead of WM_USER. Such as IPC_PLAYFILE:

*/

#define IPC_PLAYFILE 100

/*

COPYDATASTRUCT cds; cds.dwData=IPC_PLAYFILE;

cds.lpData=(void *) "file.mp3"; cds.cbData=strlen¹⁾ cds10,1=char(mod(p/0x100,0x100)) cds11,1=char(mod(p/0x10000,0x100)) cds12,1=char(mod(p/0x1000000,0x100)) SendMessage(hwnd_winamp,0x4a,0,GetPointer(cds)) </code>

I have no idea if this even compiles, but hopefully this will help more than harm.

Pat

Thanks man .. i will play with this today. Of course if it doesn't work first time I will 'user it' and shake my fists sternly at the air while cussing for your trying to help

thanks again

dsig@teleport.com onmouseover=window.status=the new revelation technology .. a refreshing change;return(true)"

David Tod Sigafoos ~ SigSolutions

Phone: 503-639-4240

David,

Some of us who have done little C++ struggle with Win API structures - yet they are a geat enabler to OI, opening up a rich resourse. We sruggle needlessly on the prototype, and its implimentation instead of being able to just wack it in and get on with our project. How many projects stall with the prize in our grasp because it seems too dificult.

Some of us (well me) would like to see a works area / catalog of published Win API prototypes, maybe with some associated examples of declaration and use. The concept is that members could contribute prototypes, they could be published as verified / not verified. Over time we would build an extensive array of resources to extend the dase system - enabling us to be more productive.

Richard Bright

BrightIdeas New Zealand

I'd like to see that too!

That would be a great idea .. lord knows I can use all the help I can get when it comes to bits ..

dsig@sigafoos.org.com onmouseover=window.status=the new revelation technology .. a refreshing change;return(true)"

David Tod Sigafoos ~ SigSolutions

Phone: 503-639-4240

Pat ..

You are lucky you aren't close .. I would have to come over and give you a big hug and maybe a little kiss on the cheek.

Imagine my HoHumm attitude when I entered your code and it worked the first time

THanks alot .. but never fear the are new questions coming

dsig@sigafoos.org.com onmouseover=window.status=the new revelation technology .. a refreshing change;return(true)"

David Tod Sigafoos ~ SigSolutions

Phone: 503-639-4240

Richard,

I support that idea of a catalog of published Win API prototypes!!!

- Oystein -

Guys-

We've started to do this, by putting the API changes into the product. Specifically, we added some to OI 4.0.x as a result of Don Bakke's request during beta.

Send us the ones that you have, with documentation. We'll put them into the product, and then we'll release a technical Bulletin (Yes, they are re-appearing based upon feedback at the conference) with the details.

Figure that we'll do this post 4.1 release, so sometime in September.

Thanks-

Mike

View this thread on the forum...