Esclapion

[luebking]

Esclapion

[luebking]

• How do you invoke it?
• did you compare the zenity behavior?
• what kind of shell (bash, dash, zsh, ...) invokes it?

"--progress --auto-close" is supposed to automatically close once you reach 100% and "--progress --auto-kill" is supposed to cancel the parenting script when canceled.
Both work as expected here.

[Esclapion]

Hi,

I work now on a lxqt, and I have a tool written in bash who calls zenity
for a progress bar.
zenity is qt-based, and I wish to change it by qampa to change from Gtk to
qt4 (ot 5).

To verify that your tool worked as zenity, I took some examples on the Net.
On some, it's the case, but I ecnountered a problem withe the progress bar.

If I take the 1st example here :

https://help.gnome.org/users/zenity/stable/progress.html.en

it works well with zenity. But if I add at the begin :

alias zenity=qampa

I see the progress, but it never ends. And if I click on Cancel, the
following instructions are not executed. So, two probs.

I will try with --auto-close, thanks.

Greetings,

Patrice (aka Esclapion, Manjaro support team)

2014-07-23 20:53 GMT+02:00 luebking [email protected]:

• How do you invoke it?
• did you compare the zenity behavior?
• what kind of shell (bash, dash, zsh, ...) invokes it?

"--progress --auto-close" is supposed to automatically close once you
reach 100% and "--progress --auto-kill" is supposed to cancel the parenting
script when canceled.
Both work as expected here.

—
Reply to this email directly or view it on GitHub
#1 (comment).

[luebking]

Thanks for the link.
I tested it with qarma and zenity (3.12.1)

Zenity does not close the dialog automatically, but has an additional "ok" button and activates it when reaching 100%
-> This needs to be added to qarma.

Both will (as can be expected) continue the script when cancelled (add "echo foobar" to the end to check) but neither qarma nor zenity exit with "-1" (but exit code "1") when cancelled, so the error dialog isn't spawned in either case.

What does /bin/sh link for you? (bash? dash? zsh? ...)

[Esclapion]

What does /bin/sh link for you? (bash? dash? zsh? ...)

bash. It's the default in Arch and in Arch-based distros. But I knw there
is a trend for zsh. All our scripts are written for bash.

2014-07-24 15:22 GMT+02:00 luebking [email protected]:

Thanks for the link.
I tested it with qarma and zenity (3.12.1)

Zenity does not close the dialog automatically, but has an additional
"ok" button and activates it when reaching 100%
-> This needs to be added to qarma.

Both will (as can be expected) continue the script when cancelled (add
"echo foobar" to the end to check) but neither qarma nor zenity exit with
"-1" (but exit code "1") when cancelled, so the error dialog isn't spawned
in either case.

What does /bin/sh link for you? (bash? dash? zsh? ...)

—
Reply to this email directly or view it on GitHub
#1 (comment).

[luebking]

Please see commit 60ca43e

Another thing I noticed is that Qt automatically closes QProgressDialog when you set a value > 0, but neither issues accepted nor rejected, ie. the qarma process just continues.
Maybe this is related to your problem? (resolved as well)

[Esclapion]

Thanks, nice job, solved for this. :-) But a title is missing here :

qarma --progress --width 650 --auto-close --title "${M[11]}"" $NomIso"

I send you the program (to run as root), it's intended to copy an ISO on an
USB Key. I only replaced all zenity with karma.

If you have also zeniy, you will see the difference. I think it's only a
little thing, but ?

2014-07-24 15:56 GMT+02:00 luebking [email protected]:

Please see commit 60ca43e
60ca43e

Another thing I noticed is that Qt automatically closes QProgressDialog
when you set a value > 0, but neither issues accepted nor rejected, ie. the
qarma process just continues.
Maybe this is related to your problem? (resolved as well)

—
Reply to this email directly or view it on GitHub
#1 (comment).

[luebking]

In case you attached something to the mail, i'm not sure whether the github issue tracker (you're mailing to that, not me) can handle attachments.

The title should be shown in the window decoration provided by the window manager.
Zenity does not add any other label, but meanwhile uses client side decorations.

You could attach a screenshot stressing what you miss, but need to visit the link at the bottom of this mail.

[Esclapion]

What I did, but probably an error :-( I have pastebin that here :

http://pastebin.com/9n1A76PG

at the end, with :

qarma --progress --width 650 --auto-close --title "${M[11]}"" $NomIso"

The title must be : "copy of the ISO name.iso" and I have nothing. A window
with the title qarma, a progressbar, nothing else.

It works, but... I can change the script, if necessary, but I dont
understand what happens.

2014-07-24 23:07 GMT+02:00 luebking [email protected]:

In case you attached something to the mail, i'm not sure whether the
github issue tracker (you're mailing to that, not me) can handle
attachments.

The title should be shown in the window decoration provided by the window
manager.
Zenity does not add any other label, but meanwhile uses client side
decorations.

You could attach a screenshot stressing what you miss, but need to visit
the link at the bottom of this mail.

—
Reply to this email directly or view it on GitHub
#1 (comment).

[luebking]

Do you get an expected title for
qarma --progress --width 650 --auto-close --title "Foo Bar"

[Esclapion]

I changed the line for :

done) | qarma --progress --width 650 --auto-close --title "Essai"

and nope. I don't see "Essai".

2014-07-24 23:30 GMT+02:00 luebking [email protected]:

Do you get an expected title for
qarma --progress --width 650 --auto-close --title "Foo Bar"

—
Reply to this email directly or view it on GitHub
#1 (comment).

[luebking]

Ah. Qt5 - no problem with Qt4

I assume the QApplication parser of Qt5 sucks the title parameter away.

[Esclapion]

I'm now under xfce for the moment. But my goal is a lxqt ported recently in
qt5.

2014-07-25 0:22 GMT+02:00 luebking [email protected]:

Ah. Qt5 - no problem with Qt4

I assume the QApplication parser of Qt5 sucks the title parameter away.

—
Reply to this email directly or view it on GitHub
#1 (comment).

[luebking]

Yes, I was just mentioning. The goal is to have this work in either case ;-)

[Esclapion]

afaik, Qt5 has less things than Qt4. The devs of lxqt complained about that.

2014-07-25 0:33 GMT+02:00 luebking [email protected]:

Yes, I was just mentioning. The goal is to have this work in either case
;-)

—
Reply to this email directly or view it on GitHub
#1 (comment).

[luebking]

That's not the problem here.
Qt5 interprets the switch and removes it from the arguement list. Then sets it on the first shown QWindow.
For some reason, this does not work with QDialog.

I either need to figure why or extract the switch from the vanilla argument list.

[luebking]

See commit 827c59d
Current master also fixes two issues on custom labels (if you care)

[luebking]

I'm closing this as the original issue is confirmed to be resolved. The --title in Qt5 should now work as well.
Please do not hesitate to open a new item as soon as you spot another issue.

Many thanks for testing and reporting.

[Esclapion]

Works, thanks a lot. FYI :

https://forum.manjaro.org/index.php?topic=15425.msg142735#msg142735

Regards

2014-07-26 11:36 GMT+02:00 luebking [email protected]:

I'm closing this as the original issue is confirmed to be resolved. The
--title in Qt5 should now work as well.
Please do not hesitate to open a new item as soon as you spot another
issue.

Many thanks for testing and reporting.

—
Reply to this email directly or view it on GitHub
#1 (comment).