[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: Entry "changed"
- From: Eric Harlow <linuxgeek yahoo com>
- To: gtk-app-devel-list redhat com
- Subject: Re: Entry "changed"
- Date: Thu, 17 Jun 1999 12:12:36 -0700 (PDT)
Could just put a simple check in the "changed" callback which checks
the value.
if (old_value != new_value) {
old_value = new_value;
/* really changed */
}
Could also do some kind of locking mechanism.
if (!being_updated) {
being_updated = true;
// --- Update code
being_updated = false;
}
Assuming that it's a global or procedure level static variable.
-Eric
--- "Scott." <scottf@scs.unr.edu> wrote:
>
> i have 2 entries that rely on each other (they scale
> an image, keeping the
> proportions).
>
> the problem is when one is changed, it calls the
> associated callback,
> which updated the text in the other one, which will
> then call the same
> callback which will update the text in the first
> one... and so on. :P
>
> how can i update the text in an entry and NOT have
> it emit "changed"?
>
> -=Scott
>
>
> --
> To unsubscribe: mail
> gtk-app-devel-list-request@redhat.com with
> "unsubscribe" as the Subject.
>
> Mailing list concerns should be mailed to
> <listmaster@redhat.com>
>
>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]