Re: Is there an off-by-1 bug in notification callbacks?

[Nolan Darilek]

Got it, thanks for that explanation.


Two hopefully quick follow-up questions: How do I get a connection's 
client ID? I'm trying to create a Rusty interface, so need to match 
client IDs to Rust client instances so their callbacks can be correctly 
dispatched.


Also, how do I match spoken messages with message IDs so that, at time 
of speaking, I can return some sort of ID that the client can wait for 
in its callbacks?


Thanks again.

On 8/19/20 11:02 AM, Samuel Thibault wrote:
> Samuel Thibault, le mer. 19 août 2020 17:55:18 +0200, a ecrit:
> > Samuel Thibault, le mer. 19 août 2020 17:52:45 +0200, a ecrit:
> > > Nolan Darilek, le mer. 19 août 2020 10:38:56 -0500, a ecrit:
> > > > OK, sort of figured it out--I'm not strong in the C. :) Looks like the state
> > > > parameter is the index into the enum values, not the value itself.
> > > It's not the index, it's the binary weight
> That being said, it does not seem to be actually needed to be so. The
> thing is this:
>
> > Note the difference between SPDNotificationType and SPDNotification.
> you are getting a SPDNotificationType, not a SPDNotification, so you
> have to use values from SPDNotificationType.
>
> Samuel