Re: FileChooserDialog and response signal

[José Alburquerque <jaalburquerque cox net>]

Marcus Brinkmann wrote:
> At Tue, 27 May 2008 23:34:45 +0200,
> Murray Cumming <murrayc murrayc com> wrote:
>   
> > On Tue, 2008-05-27 at 18:48 +0200, Marcus Brinkmann wrote:
> >     
> > > I don't know a way to squeeze a signal handler before its own
> > >   handler.  See gtkfilechooserdialog.c:
> > >       
> > connect_notify() can do this,
> > or you can just call connect() with false for the optional extra
> > parameter:
> >     
>
> This does not appear to be the case.  The signal handler does not only
> need to run before the default handler, but even before the signal
> handler connected by the FileChooserDialog implementation.  Again, see
> the cited comment in the Gtk+2 source file. GtkFileChooserDialog does
> not override the default signal handler, but connects to it like a
> user explicitely to run before anything else.
>
> I tried your suggestion and as to be expected, the signal handler
> connected later is also run later, irregardless of the argument to
> connect.
>   

I tried your c++ example on this system (debian GNU/Linux lenny/sid) 
with Murray's suggestions and both suggestions (connect_notify and 
connect with false parameter) detect an overwrite asking if file should 
be replaced, just as the C version.  What system are you running?

> Thanks,
> Marcus
>
> _______________________________________________
> gtkmm-list mailing list
> gtkmm-list gnome org
> http://mail.gnome.org/mailman/listinfo/gtkmm-list
>
>   


--
José Alburquerque
jaalburquerque cox net

The path to real wisdom begins with a deep loving respect for the ever living God (Prov. 1:7)