Maybe this its not the best place to ask , But I want to know how I make that all the windows that I open fits on my 640x480 resolution??

What you could try is to go to /usr/bin (/usr/sbin?) and find the gtkdialog binary, rename it gtkdialog.bin, then right-click in the Rox window and select New->Script and create a script named gtkdialog.
Open the script and add to it:

Code:

exec gtkdialog.bin "$*" --geometry=640x480

and see if it helps... I think Thunor fixed it to show scrollbars._________________What's the ugliest part of your body?
Some say your nose
Some say your toes
But I think it's your mind

was working fine in Pupdial and Pnethood as far as I know. It formerly showed a row of x's (xxxxxxx) to blank the password, now there is no x's and no anything (no visible entry when typing, variable is fine though on exit) I guess though that is the expected result and the old way was a buggy side effect.

There is a syntax I wasn't aware of that shows dots for the password..

By replacing <progressbar> by <timer> in Pprocess, the pid handling become much better.

Excellent, and you're welcome.

zigbert wrote:

There is a misbehavior in the menu widget. I think (really sure) that this has arrived with 0.7.21.
...
This happens for icon="gtk-save" and gtk-info as well. I have not checked all, but many works as expected.

A sidenote: The menubar example still uses <seperator> instead of <menuitemseperator>

I couldn't see anything wrong with your example. I added entries for gtk-save and gtk-info as well and took and attached a screenshot (I'm using lupu-520 with the GTK+ 2 Crux theme).

[EDIT] I use /usr/sbin/gtkdialog so I still have the /usr/sbin/gtkdialog3 0.7.20 Patriot Edition which I tried and all the icons are present except that originally menuitem theme icons from icon="imagename" were hardcoded to 20px whereas I set them to 16px (the GTK+ function that loads theme icons ultimately chooses the size from the nearest available).

There is a backward compat issue that has surfaced.
...
It formerly showed a row of x's (xxxxxxx) to blank the password, now there is no x's and no anything...

I've found the issue

Firstly I should point out that both "invisible-char" and "visibility" are GTK+ properties and all that Gtkdialog does with them is pass them onto GTK+ to set.

A short while back I fixed some code that was passing variables of type guint (GTK+ unsigned integer) to GTK+ as a gchar, and this was the reason why "border-width" never worked before. Well, "invisible-char" is a guint but because the code was bugged and sending the value to GTK+ as a gchar, the value shown in the examples is "x" when it should've been "120" Therefore the Gtkdialog documented "invisible-char" is wrong.

"invisible-char" isn't even required as GTK+ uses a default asterisk according to the documentation, so the visibility="false" tag attribute or the <sensitive>password</sensitive> directive should suffice.

Yes, the <sensitive>password</sensitive> directive works (I deprecated <visible> but you can still use it).

Hopefully, that's all you plan to do with it. The Samba-TNG client tools have always used the <visible> tag to hide passwords.

Hello rcrsn51

The <visible> directive is used to hold "enabled" or "disabled" ("password" in your case which is unique) which describes the widget's sensitive state of "true" or "false". This is equivalent to the tag attribute (GTK+ property) of sensitive="true/false" but it makes no sense whatsoever being called <visible> or holding "enabled" or "disabled" (<enabled>true/false</enabled> would be an improvement). Now, part of what I am doing is making things consistent and sensible, therefore removing <visible>enabled/disabled</visible> from the documentation and replacing it with <sensitive>true/false</sensitive> to me seems like a very sensible thing to do -- even more so when you consider that there exists a visible="false" tag attribute to hide a widget! -- but I'd have to be a complete moron to remove support for <visible> as it would break a very high percentage of every Gtkdialog application ever written.

was working fine in Pupdial and Pnethood as far as I know. It formerly showed a row of x's (xxxxxxx) to blank the password, now there is no x's and no anything (no visible entry when typing, variable is fine though on exit) I guess though that is the expected result and the old way was a buggy side effect.

There is a syntax I wasn't aware of that shows dots for the password..

to make a style for something unusual in the dialog boxes. Doing this could be automated. I can do it by putting a wrapper script around gtkdialog that loos for the "<style>" tag and makes the file needed and then removes it again after the dialog is closed. This could also be built into the gtkdialog.

8-bit: invisible_char="x" is an error in the original Gtkdialog documentation but it worked because the Gtkdialog C code that passed "x" to GTK+ to set was bugged. In fact ALL guint GTK+ properties would've been affected by this bug, but I don't think that there are many of them.

Nothing within the second example is being changed to break anything. <visible>password</visible> has always worked and will always work.

When you say "Enter_OK code", are you describing pressing the Enter key within an entry widget to activate a default OK button? If so the very first entry widget in the entry example does exactly this. I've also connected-up the "activate" signal so that it is emitted when pressing Enter within the widget which can be used to do anything you wish. I recommend that you play with the example.

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