...
Made the changes you suggested - did not change behaviour on Upup Precise 54x4......still warning and not possible to select tab#1
...

I've been studying the snap2 code and this is how I think it works:

There's a big while loop at line 249 which looks as though it envelopes the entire application and this is used to restart it. When the main dialog exits, its output is evaluated and if you haven't supplied some necessary information then you'll get a warning in a message box, a variable called maintab will be set to something and then it goes back to the top of the while loop and runs again which will present the tab associated with the widget that you must enter data into.

You should see the main dialog first (line 659), then the message box (line 1288) and then the main dialog restarts showing the BACKUP STORAGE tab. Well, that's under normal operation if the conditions are met at line 1286 -- $dst = "none" or $dst = "". So, you're seeing the message box first, then the main dialog showing the BACKUP STORAGE tab (#2), then you click the DIRECTORIES TO BACK UP tab (#1) which causes the same message box to reappear (is the main dialog still open now or not?).

I'm going to guess that the execution of the main dialog at line 659 initially falied, but you can't tell because all of the output is being captured in a variable, evaluated and then discarded and because it didn't run, there's no valid output to evaluate so $dst = "none" or $dst = "" causes the messsage box to appear. Then we go back to the top of the while loop and do it again but this time the main dialog does appear and then I don't know after that. There's a possibility that something on the DIRECTORIES TO BACK UP tab (#1) is causing it to crash but this isn't activated when the application restarts showing the BACKUP STORAGE tab (#2) which is why you can see it. Sherlock Holmes: eat my deerstalker

I recommend that above the code that invokes the main dialog (line 659) you should simply try $GTKDIALOG --program=MAIN_DIALOG; exit and then dump the output here. You'll want to put this underneath the debugging message #echo "$MAIN_DIALOG" which is at line 655.

Regards,
ThunorLast edited by thunor on Wed 12 Dec 2012, 11:22; edited 2 times in total

I tried gtkdialog -f ./snap2_MAIN_DIALOG in Upup Precise 54x4 with gtkdialog version 0.8.3 r493 and it loaded ok for me.

Leave it with me for a while. It would be useful if you could checkout, compile and install the latest gtkdialog from SVN (I explained how to do it earlier). Locate the current gtkdialog binary (/usr/sbin/gtkdialog?) and copy the newly compiled one onto it, then run snap2 again and see if it works. I don't need any more output now.

If it's ok, I'll make you a special version of gtkdialog which you can try later on.

It would be useful if you could checkout, compile and install the latest gtkdialog from SVN (I explained how to do it earlier). Locate the current gtkdialog binary (/usr/sbin/gtkdialog?) and copy the newly compiled one onto it, then run snap2 again and see if it works.

Thanks for all your help....
I'll report in the Snap2 thread the results....and point lstandish to the improvements you have suggested along the way.
...

Cheers for your help and it's good that it works.

Via the magic of SVN revision logs I've got a good idea what that was:

November 16th r472 I connected-up the realize signal since it was half way there anyway but I experienced an instability later on because something was NULL that I wasn't expecting so I fixed it on November 30th r483, therefore I would recommend that if somebody has a version of gtkdialog that is r472 to r482 inclusive then they might want to consider upgrading to the latest version.

I'm all done with adding features to gtkdialog for the moment and am only hanging around making sure any potential problems are resolved, so what's in SVN now (r493) is pretty much what the next source package release is going to be.

You might want to explain to lstandish that I recommend adding the " | grep =" to the end of the seven lines of code where gtkdialog is executed so that he is only evaluating the printed variables. He could also either fix the warnings or discard them by following gtkdialog with " 2> /dev/null" or not worry about it since " | grep =" will filter them out anyway.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum