Re: Odd iagno behaviour; gtk change in 1.2.5?

[Ian Peters <itp gnu org>]

On Sat, Sep 25, 1999 at 12:34:09PM +0200, Tim Janik wrote:
> 1.2.5 did indeed change behaviour a bit again with configure events (as did
> 1.2.4), in contrast to 1.2.3, gtk applications will now handle *all*
> configure events at the gtk level (while we previously used to discard some
> at the gdk level). the core gtk code now heavily relies on getting configure
> events, so if you really wouldn't get any, applications would be really
> broken, i.e. not redrawing and size allocating and similar stuff.

Quite right.  And I am getting some configure_events, just not one in
particular that I used to.

> try running your app with --gdk-debug=events (you need to have compiled
> gtk/gdk with --enable-debug=yes for that) and you'll see you are actually
> getting them.

Hrrm, I'll have to look for time to do that.  In the meantime, I've
been adding printf's at the top of my handlers, and seeing when
they're called...

Interesting.  I'd managed to fix things up by manually calling my
configure_event handler before gtk_main, but I just found that by
connecting to the configure of the window instead of the drawing area,
the problem disappears.

> i suspect you do something else wrong in your code, could you tell us how
> to exactly reproduce your problem?

Hrrm.  I have no idea what that code does anymore... :)

I'll let you know if it crops up again, but I wouldn't worry about it.
Blame it on this programmers error.

-- 
Ian Peters  | GnuPG Key ID 5C23D20C    | "They shout about love but when push
itp@gnu.org | E584 2558 FAC3 BEAB EFAC |  comes to shove, they live for things
itp@acm.org | FC74 CFED 7E24 5C23 D20C |  they're afraid of." -- Neal Peart