Re: [gtk-list] Re: coordinating idle events and redraws
- From: Tim Janik <timj gimp org>
- To: gtk-list redhat com
- Subject: Re: [gtk-list] Re: coordinating idle events and redraws
- Date: Fri, 13 Feb 1998 00:16:47 +0100 (CET)
On Thu, 12 Feb 1998, Marc Ewing wrote:
> Owen Taylor <owt1@cornell.edu> writes:
> > Keeping a single prioritized idle queue seems better to me.
> > It is more flexible, about as easy to implement, and I tend
> > to think of the main loop as providing generic event loop
> > functionality in a way that is somewhat separate from the
> > rest of GTK. So I'd rather put in a general facility than
> > a special case for the drawing/resizing code.
>
> Agreed. That's cleaner.
>
> > It's probably easier for me to do it. I'm going to change things
> > around with gtk_idle_add anyways as part of the _interp() changes,
> > and I'm already pretty familiar with that part of the code.
> >
> > Assuming that it goes as easily as I think, I'll do it this
> > evening.
>
> Cool. Btw, I've just hacked priorities into my copy and it solves
> my little redraw/idle problem. I don't have general integer
> priorities though - just a enum with low, default, and high. It
> seemed more mnemonic than integers. But either way is fine with me.
if we are really going to implement there should be defines like
#define GTK_PRIORITY_LEAST (10)
#define GTK_PRIORITY_DEFAULT (0)
#define GTK_PRIORITY_HIGHEST (-10)
so you can scale idle hanlders between the extrema.
>
> -Marc
>
---
ciaoTJ
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]