Re: [gupnp] problem with GUPnPLastChangeParser

[Sven Neumann <s neumann raumfeld com>]

Hi,

On Wed, 2009-04-29 at 19:55 +0300, Zeeshan Ali (Khattak) wrote:

> > But there's still a problem. Consider an unsigned int variable where the
> > whole range of possible values is allowed and valid. How would I deal
> > with such a value given the current API of GUPnPLastChangeParser?
> 
>    True but what are the chances of you needing all the possible
> values of gint64?

I can't use a gint64 variable here. If the LastChange event holds an
UINT variable, then I need to pass a pointer to a guint variable.

>  Also if you are sent a value that is the same as you
> already had, is there really a need to know if it was sent or not?

That is actually a good suggestion. Initializing the variable to the
known value solves the problem. Thanks.

The code is still buggy though and we should try to come up with a patch
for it.


Sven


--
To unsubscribe send a mail to gupnp+unsubscribe\@o-hand.com