I confirm the problem was on Windows XP. I do not have another OS handy to
try. THanks all
Firat Ozgul wrote:
>
> I tested the original poster's code on Ubuntu Karmic Koala (GNOME). As
> soon
> as the file dialog is closed, the entry widget is ready for typing. So it
> seems that this problem
-discuss] Entry Widget that can't enter into at first.
I tested the original poster's code on Ubuntu Karmic Koala (GNOME). As soon as
the file dialog is closed, the entry widget is ready for typing. So it seems
that this problem is specific to Windows OS.
2010/8/24 Cameron Laird
On Tue, Au
It is Debian, after all... :)
By the way, I created a new record for this issue with Cameron Laird's
suggestion:
http://bugs.python.org/issue9673
Cheers,
Firat
2010/8/24 Michael Lange
>
> Here it is a debian linux with IceWM running where I could *not* reproduce
> the error :)
>
> Regards
>
>
Thus spoketh Firat Ozgul
unto us on Tue, 24 Aug 2010 15:36:56 +0300:
> I could reproduce the error on a Windows XP machine. I will test it on
> GNU/Linux (Ubuntu Karmic Koala - GNOME) in the evening.
>
Here it is a debian linux with IceWM running where I could *not* reproduce
the error :)
Reg
I tested the original poster's code on Ubuntu Karmic Koala (GNOME). As soon
as the file dialog is closed, the entry widget is ready for typing. So it
seems that this problem is specific to Windows OS.
2010/8/24 Cameron Laird
> On Tue, Aug 24, 2010 at 03:36:56PM +0300, Firat Ozgul wrote:
>
I could reproduce the error on a Windows XP machine. I will test it on
GNU/Linux (Ubuntu Karmic Koala - GNOME) in the evening.
2010/8/24 Cameron Laird
> On Tue, Aug 24, 2010 at 11:57:57AM +0300, Firat Ozgul wrote:
>.
>.
>.
>
On Tue, Aug 24, 2010 at 11:57:57AM +0300, Firat Ozgul wrote:
.
.
.
> Actually, I can reproduce the error described by the original poster... I am
> not exactly sure about the true dynamics of the solution, but after_idle()
> me
Actually, I can reproduce the error described by the original poster... I am
not exactly sure about the true dynamics of the solution, but after_idle()
method seems to solve the problem in a way. Perhaps, for one reason or the
other, the program cannot return to the main window properly even though
Hi,
Thus spoketh "wet_colored)arch"
unto us on Tue, 24 Aug 2010 00:51:32 -0700 (PDT):
>
> I cannot
> 1) enter content into the entry field without first trying to quit and
> then cancelling - I cannot expect the user to do this because it is not
> intuitive. I should be able to enter the en
Hi,
Its always better if you provide code which can be run. Reduce
out all irrelevant code. (often this process shows you the problem
in your code).
If you have an askyesno dialogue open, that hogs the keyboard,
so you cannot type to another window while it is open.
Mick
>>> >>
Hi,
Its always better if you provide code which can be run. Reduce
out all irrelevant code. (often this process shows you the problem
in your code).
If you have an askyesno dialogue open, that hogs the keyboard,
so you cannot type to another window while it is open.
Mick
On Tue, Aug 17, 2010
What basically happens is if I use the application all features work fine
except the entry widget I have created. I cannot add text or even get the
cursor to appear in the entry field.
What is odd is I have a askyesno button for quiting. If I hit "no" and
return to the application, I can then en
12 matches
Mail list logo
