Re: [pygtk] gtk.MessageDialog core

2003-11-04 Thread Christian Robottom Reis
On Fri, Oct 31, 2003 at 11:58:12AM +, Gustavo J. A. M. Carneiro wrote: Well, it's gtk+/C's fault, not pygtk's. It seems that gtk+ doesn't like when you connect to focus-out-event and run a nested main loop inside the handler (dialog.run). The GtkEntry widget expects to receive the

Re: [pygtk] gtk.MessageDialog core

2003-11-04 Thread Christian Robottom Reis
On Mon, Nov 03, 2003 at 03:12:31PM -0400, Fernando San Martin W. wrote: On Fri, 31 Oct 2003 11:58:12 +, Gustavo J. A. M. Carneiro wrote i report the bug to bugzilla.gnome.org, so they told this: + +--- Additional Comments From [EMAIL PROTECTED] 2003-11-03 11:45 --- +Maybe

Re: [pygtk] gtk.MessageDialog core

2003-11-03 Thread Fernando San Martin W.
On Fri, 31 Oct 2003 11:58:12 +, Gustavo J. A. M. Carneiro wrote i report the bug to bugzilla.gnome.org, so they told this: + +--- Additional Comments From [EMAIL PROTECTED] 2003-11-03 11:45 --- +Maybe pygtk is not getting the return value from the signal +handler right? I'd need a C

Re: [pygtk] gtk.MessageDialog core

2003-10-31 Thread Fernando San Martin W.
On Thu, 30 Oct 2003 21:22:13 -0200, Christian Robottom Reis wrote On Thu, Oct 30, 2003 at 03:40:11PM -0400, Fernando San Martin W. wrote: i tested in some diferents machines and i have the same problem, this code is executed by key_press_event on an gtk.entry to advice if something is wrong

Re: [pygtk] gtk.MessageDialog core

2003-10-31 Thread Fernando San Martin W.
On Fri, 31 Oct 2003 07:37:52 -0400, Fernando San Martin W. wrote i try this: import gobject import gtk from gtk import TRUE, FALSE def mainwin(): def advice(): m = unicode(Atención, 'latin-1') dialog =

Re: [pygtk] gtk.MessageDialog core

2003-10-31 Thread Gustavo J. A. M. Carneiro
Well, it's gtk+/C's fault, not pygtk's. It seems that gtk+ doesn't like when you connect to focus-out-event and run a nested main loop inside the handler (dialog.run). The GtkEntry widget expects to receive the event soon. Maybe you should bring this up in the gtk list, or file bug report

[pygtk] gtk.MessageDialog core

2003-10-30 Thread Fernando San Martin W.
hello: i'm runnig this code: m = unicode(mensaje, 'latin-1') dialog = gtk.MessageDialog(window, gtk.DIALOG_MODAL | gtk.DIALOG_DESTROY_WITH_PARENT,gtk.MESSAGE_INFO, gtk.BUTTONS_OK, m.encode('utf-8')) dialog.run() dialog.destroy() the message dialog is

Re: [pygtk] gtk.MessageDialog core

2003-10-30 Thread Fernando San Martin W.
On Thu, 30 Oct 2003 19:13:48 +, Gustavo J. A. M. Carneiro wrote A Qui, 2003-10-30 às 18:30, Fernando San Martin W. escreveu: hello: i'm runnig this code: m = unicode(mensaje, 'latin-1') dialog = gtk.MessageDialog(window, gtk.DIALOG_MODAL |

Re: [pygtk] gtk.MessageDialog core

2003-10-30 Thread Gustavo J. A. M. Carneiro
A Qui, 2003-10-30 às 18:30, Fernando San Martin W. escreveu: hello: i'm runnig this code: m = unicode(mensaje, 'latin-1') dialog = gtk.MessageDialog(window, gtk.DIALOG_MODAL | gtk.DIALOG_DESTROY_WITH_PARENT,gtk.MESSAGE_INFO, gtk.BUTTONS_OK, m.encode('utf-8'))

Re: [pygtk] gtk.MessageDialog core

2003-10-30 Thread Christian Robottom Reis
On Thu, Oct 30, 2003 at 03:40:11PM -0400, Fernando San Martin W. wrote: i tested in some diferents machines and i have the same problem, this code is executed by key_press_event on an gtk.entry to advice if something is wrong with the data entered in the entry Can you try to produce a minimal