Thank you for educating me on the history. I agree that Xdialog and gtkdialog alone are more than enough to cover all the use cases.mikeb wrote:yaf-splash was introduced around puppy 2.17 iirc, last of the 2 series . GTK2 has been in puppy since at least 1.08.
Xdialog , gxmessage and gtkdialog were used and present before yaf splash. ...xmessage was retained rather than gxmessage cos it looked worse I assume.
So it was brought in when there were perfectly useable, visually pleasant tools, then thrown out again after many scripts were changed over and now there is a very hacky inefficient script to replace it and a series of confusing symlinks and a half hidden original binary.... all seems like a waste of peoples time thats all.
LOL yes you need to edit some (horrible horrible!) C code. Screenshot attached.wonder why thats was not done... perhaps because it required more than a bash script ?. In fact, it is quite straightforward to enable yaf-splash to work with UTF-8 string (I just did that)
Hold that radish just yet. Add LD_LIBRARY_PATH=/usr/X11R7/lib:$LD_LIBRARY_PATH to your ip-up script. See if that helps.jafadmin wrote:Well, this didn't survive a reboot. It worked for hours, then for some inexplicable reason, just quit after a reboot.
Now I can't get it to work from a LiveCD.
Weirdness. Absolute weirdness ...
My best guess is that pppd is altering the environment in some way that breaks yaf-splash.
If I just execute the ip-up script stand-alone, yaf-splash works as expected. If the ip-up script is executed by the pppd process, it doesn't.
I'm gonna take up radish farming.