# NOTE: This example requires at least gtkdialog-0.7.21 (please visit
# http://code.google.com/p/gtkdialog/). Additionally if you are using
# Puppy Linux then you may find that an historical version of gtkdialog
# already exists in /usr/sbin, and if that is the case then you should
# modify the shell variable below to point to the new gtkdialog binary.

# NOTE: The following image names should hopefully represent physical
# files that exist upon your computer minus their paths and extensions,
# but if you find them to be missing then substitute them with something
# that you do have within /usr/share/icons or /usr/share/pixmaps.

Doing it this way makes GTK+ deal with the left-to-right and right-to-left internationalisation of the icons if applicable. You might be thinking that this isn't going to work because GTK+ will make a stock label "_Undo" and it will, but straight afterwards it will update the label with $LOC118 or $LOC119 and additionally because it was initially a stock label, "use-underline" is already true so you can use underscores in your custom text.

Actually I think that this qualifies as a Gtkdialog Tip

Regards,
Thunor

01micko-menuitem-icon-issue.gif

Description

I added underscores to demonstrate that "use-underline" is automatically true

Guys,
I'm pissed off. It is nice that gtkdialog is getting developed, but I was caught unawares.

Ok, there was the bug with password-entry box having invisible text, only two apps needed to be fixed. Although, I still don't see why the original syntax couldn't have continued to be supported.

I released Wary Puppy 5.1.4 a couple of days ago, then yesterday I discovered that Pfind is broken, as the directory-select dialog is broken. I informed zigbert, and he finds the bug and then informs me that this means Pburn, Pmirror and Pbackup are also broken.

Ok, I will bring out an emergency upgrade to Wary Puppy, but I'm not happy.

The 'common' repo currently has gtkdialog revision 224, and that's it. I'm not going to upgrade. If you bring out strict bugfixes for that, fine. Any further development should be in a separate development thread. All apps that are to be publicaly released should be tested to work on the reference gtkdialog as available in the 'common' repo at ibiblio.org.

I don't intend to upgrade gtkdialog again unless there is a very good reason to do so, nor will I upgrade any more apps that use gtkdialog unless they are tested against that version of gtkdialog._________________http://barryk.org/news/

You have no need to be. This is a development release, and you are the one to choose to include this code. I find it rather ambitious to include 'new' libs/backends in bugfix releases.

I have not used any new gtkdialog features in my scripts else of Pmusic 2 and the latest pprocess (because of much better performance). My intentions is to start using 0.7.21 at once it is released as stable.

yesterday I discovered that Pfind is broken, as the directory-select dialog is broken.

Very important. The directory-select dialog is not broken. In fact it is now working. My way of adding too much lines into the xml-code was ignored by gtkdialog-0.7.20. Now my dirty lines actually executes and *ucks up the result.

MY FAULT

I think we should encourage Thunors initiative... which could give Puppy a boost.

The way I see it is that Pere Laszlo's s original gtkdialog is quite buggy and we have been used to coding to suit the bugs. Thankfully we have someone with the ability to fix the bugs and provide us the correct syntax to improve and enhance gtkdialog.

Sure, there is a transitional period where some things may not work as expected. We have been assured that backward compatibility is not broken.. I believe this.. it's our bad ways that are broken .

It's our responsibility as coders to fix what's not right!

I think that it's really important for Puppy's future that gtkdiaog is fixed and further developed.

yesterday I discovered that Pfind is broken, as the directory-select dialog is broken.

Very important. The directory-select dialog is not broken. In fact it is now working.

You are playing with words here. Pfind was broken, full stop. The fact that it relied on quirks in an earlier release of gtkdialog is a different matter.

From what I read awhile back, I think that thunor stated that existing scripts would be supported. So, in good faith I started to use the gtkdialog versions from SVN.

Then I got into some pressure to keep upgrading from SVN. It was not just your Pprocess, but also latest Pnethood and Wallpaper that use the new features of gtkdialog. Then I went to revision 224 when it was reported to have fixed a bug introduced in an earlier revision.

I really didn't have much choice but to use the "development version", given that app coders, not just yourself are embracing it.

Yes, I am keen to encourage thunor also, but we have so many scripts out there that use gtkdialog, and we don't know now which of them are now broken. We have only tested some apps. More changes are coming to gtkdialog at a rapid pace, so what else is going to get broken?
That is why I am stopping at revision 224._________________http://barryk.org/news/

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