Puppy Linux Discussion Forum

[8-bit]

I had downloaded and compiled the source on June 27th at 9:37 am.
I had no problems with the close or exit buttons in programs.
What programs did you use for reference to verify this?

[smokey01]

It was only the button in partview. The other apps I tested, the close button seem to work ok.

I think the problem is with partview not gtkdialog.

[pemasu]

I was sure I got nonworking quit button with some other gtkdialog application also. I recompiled the latest gtkdialog again. I cant reproduce the problem with any other than Partview, all the other apps I tested works as it should. Reverting back to the Patriots gtkdialog version restores the Partview Quit button usage.

Sorry, it seems there is so far only Partview in my Puppies which does not work as it should.
I have used in woof partview-2.1.pet. It is from quirky repo.
http://distro.ibiblio.org/quirky/pet_packages-quirky/partview-2.1.pet

[thunor]

[zigbert]

[pemasu]

Thunor. Thank you of your quick testing, fix and report. I will retest new gtkdialog3 when it is time and will include it to the next version of my puppy. It seems nice way to find some problems and it will benefit all to get them hunted.

[01micko]

Funny that glade bug is not apparent in spup. Anyway, new spup will be soon and I'll include the latest gtkdialog revision too (and perhaps some other gtkdialog goodies )

[8-bit]

I have been playing with the child window that patriot so kindly made work.
I found that by including a text area with a variable for the child process, I could add a child that was a lot more than just a text box.
I then proceeded to add another child process to see if more than one was supported.
It is. But it is a one way thing. The first child process in the script must be launched first or the script will crash.
But after starting both child processes, either can be closed from the main dialog.
It was an interesting experience though.
And for the curious, I actually used one of the gtkdialog examples of tree stock icons as a child process.
Also, the example in usr/share/doc/gtkdialog3/examples/01.02-button_action_types needs the addition of a variable statement to work correctly as to closing the child from the child window.

[Argolance]

Hello,
Thank a lot to zigbert for GtkDialog tips which are so clever and... useful!
Question:
In the script showing how to move items in list by drag'n drop...

[8-bit]

I am not sure how one could code it, but it seems that the button-release-event that calls the move function is not at fault.
Instead, the button-press-event would call another function to note the cursor position in a variable and then the move function would check that variable for a change of cursor position.
If it was the same, the move would be aborted.

[Argolance]

Hello 8-bit,
Thanks for your reply.

[8-bit]

Argolance nad others,
If you want to see my solution to the drag example list disappearing, go
HERE.

It may not be the best, but it works.
And by the way, I found all I needed on this forum!

[Argolance]

Thank you a lot!

[8-bit]

When one is writing a gtkdialog script, there seems to be no reference one can refer to as to words that are reserved for gtkdialog.
A list of those words would be nice so one knows not to use them as variables or other areas where they might conflict with reserved words.

Good idea or bad?

[Dave_G]

I've just started coding with gtkdialog and have to agree 100% with 8-bit.

Unfortunately this lack of documentation is not unique to gtkdialog, it seems
to be pretty common in the Linux world.
A very big stumbling block for newbies like myself.

Dave.