Re: Question about HostCallback_GetTransportState
Re: Question about HostCallback_GetTransportState
- Subject: Re: Question about HostCallback_GetTransportState
- From: Paul Davis <email@hidden>
- Date: Mon, 15 Aug 2011 16:35:36 -0400
On Mon, Aug 15, 2011 at 4:22 PM, Eagle Offshore <email@hidden> wrote:
> typedef OSStatus (*HostCallback_GetTransportState)
> ( void *inHostUserData,
> Boolean *outIsPlaying,
> Boolean *outTransportStateChanged,
> Float64 *outCurrentSampleInTimeLine,
> Boolean *outIsCycling,
> Float64 *outCycleStartBeat,
> Float64 *outCycleEndBeat );
> I draw your attention to "outTransportStateChanged". Really? I'm supposed
> to keep a map of every possible client that might call me back and what I
> told them last time they called the callback so I can tell them that this
> time I'm telling them something different? Is this argument used at all?
> Is it a bad idea if I just return YES all the time? Why?
your host presumably has some data structure representing a given AU.
you store the last transport state reported to that client somewhere
in that data structure, so that its per client.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden