I recommend that you compile gtkdialog yourselves and place some debugging code into it.rerwin wrote:1. Is there a way to add some debug/troubleshooting logging to gtkdialog to help identify where things go awry? Or is there already someplace to find diagnostic info from gtkdialog?
2. Because this seems, to me, to be a case where a data item is tested but is not the expected data, thus producing random results, could you examine the gtkdialog code that handles the "exit" process to look for a possible bug of that sort?
Exiting using <action type="exit">Exit-NOW</action> or similar is handled by action_exitprogram()
action_exitprogram() is called by execute_action()
execute_action() for the button clicked signal is called by button_clicked_attr()
I've just tried it myself and you have to echo $RETVALS in the frisbee script and don't forget to rename gtkdialog3 (which I did forget to do) because it's going to be "gtkdialog" wherever you put it.