On Thu, 2015-05-07 at 16:02 +0100, Richard Shann wrote:
> After experimenting with a different bit of code, I think I've found
> the
> cause of the problem: doing the widget destroy by responding to the
> "response" signal seems to be ruining the return value.
That is interesting. Indeed I had a f
On Thu, 2015-05-07 at 16:21 +0200, Stefan Salewski wrote:
> On Thu, 2015-05-07 at 13:02 +0100, Richard Shann wrote:
>
> From https://developer.gnome.org/gtk3/stable/GtkDialog.html
>
> GTK_RESPONSE_REJECT Generic response id, not used by GTK+ dialogs
> GTK_RESPONSE_ACCEPT Generic response id, not
On Thu, 2015-05-07 at 13:02 +0100, Richard Shann wrote:
>From https://developer.gnome.org/gtk3/stable/GtkDialog.html
GTK_RESPONSE_REJECT Generic response id, not used by GTK+ dialogs
GTK_RESPONSE_ACCEPT Generic response id, not used by GTK+ dialogs
Maybe try
GTK_RESPONSE_OK and GTK_RESPONSE_CAN
I wanted to pop up two buttons for the user to choose between two
options ("primary" and "secondary"), returning true or false depending
which was chosen. I tried this
gboolean
choose_option (gchar *title, gchar * primary, gchar * secondary)
{
GtkWidget *dialog;
dialog = gtk_dialog_new_with_bu
