Hi,
my suggestion is also to release as it is and fix this problem quickly
in 2.1 code line. If binary patches are needed, perhaps this will be
possible.
The evaluation of the problem is in progress. Currently there isn't a
fix or another work around as to create the button new.
Thorsten
Kirill S. Palagin wrote:
Maybe releasing as is, describing the problem in release notes and providing
binary patch (or just the file, that fixes the problem) later on, will be OK?
Regards,
K. Palagin.
-----Original Message-----
From: Pavel Janik [mailto:[EMAIL PROTECTED]
Sent: Friday, October 06, 2006 11:18 AM
To: [email protected]
Subject: Re: [qa-dev] Push buttons bug in 2.0.4-RC3
From: Andrea Pescetti <[EMAIL PROTECTED]>
Date: Thu, 05 Oct 2006 22:01:38 +0200
> If a workaround exist, I'm in favour of releasing 2.0.4
anyway, as the
> RC phase has already been too long. But if a workaround does not
It looks like you still can delete the button and create it
again from scratch.
--
Pavel Janík
... (an application) features minimal dependencies (it uses
Python/Tk)."
-- Freshmeat.net
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For
additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
