> You may follow the example > https://developer.gnome.org/gtk3/stable/ch01s04.html#id-1.2.3.12.5 Look at application code, I think it's very like the example you give me.
> This way you are not concerned with signals that match. I can't understand what you mean. > I would assume that that signal is emitted ALWAYS on the primary instance when an activation occurs. What is exactly a *activation* ? You can build the application on the repository, if you run it without args it starts normally and _activate_ gets emitted; ie: ./build/src/qsubber but if you launch with args (files) _activate_ isn't emitted. i.e. ./build/src/qsubber /home/someone/somemovie.avi Thanks, hope you understand. my english isn't so good. 2016-06-16 10:55 GMT-03:00 Stefan Salewski <m...@ssalewski.de>: > On Wed, 2016-06-15 at 12:42 -0300, Victor Aurélio Santos wrote: >> where should i do application's >> basic things like creating windows, setting-up basic things etc... > > You may follow the example > > https://developer.gnome.org/gtk3/stable/ch01s04.html#id-1.2.3.12.5 > > This way you are not concerned with signals that match. > > From > > https://developer.gnome.org/gio/unstable/GApplication.html#GApplication > -activate > > I would assume that that signal is emitted ALWAYS on the primary > instance when an activation occurs. -- Victor Aurélio Santos _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
