On Sun, 2005-02-13 at 00:08 +0100, Marc 'HE' Brockschmidt wrote:

> I've received this bug report and could reproduce it easily. I tried to
> debug this, but failed. As you naturally have no problem to understand
> the code, you can probably fix this in a few minutes.

I wish I could.  I'm seeing this bug for quite some time now but I'm
still unable to find its cause, despite many tries.  I think it's a gtk+
issue:  The bug suddenly started to appear somewhere in the 2.5 cycle
and definitely has been present ever since 2.6.0.  Whenever I try to
nail it down by writing an equivalent C app, though, that app works
flawlessly.  There must be something specific odot does that triggers
this bug -- but I've no idea what that could be.

As a (admittedly stupid) workaround, you can just hit enter after adding
a new entry.  This will create an empty node which you can then edit
normally.

-- 
Bye,
-Torsten



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to