repair-database (My first zenity script)

[glamdring]

I believe I know why now. I think its because its taking --auto-kill so long to kill the process. Any one know of a faster way to kill this process? If not i could try and make the window pop-up before the process is done being killed. But is that a wise thing to do?

EDIT:
Maybe if on clicking the cancel button it will go to another command that kills the process but displays a pulsate bar tell it is done. How can I determin what the name of the process is?

[Neal ManBear]

Try this --

Code: [Select]

if [ "$?" != "0" ]; then  # just quit
This is from ezswitch, line 105.

[glamdring]

Still doesn't like it. The only thing I can think of is to remove the cancel button, but its probably not a good idea.

But on the other hand I think I found out whats wrong with stopping the process. A lot of people are complaining about --auto-kill not working right.

[Neal ManBear]

No, the cancel button should be there for sure.

Hmm...... guess we need to look for a fix.

[Was_Just19]

Kill by PID?

[daniel]

if auto-kill, then the script dies immediately...
Use your script in a terminal, and see what is do by clicking on cancle 

[glamdring]

I do all the testing in terminal but I don't see the problem. Even removing the --auto-kill results in the slow delay to move to the next option.

Auto-kill dose indeed stop or at-least removes any changes it has made. But it takes just about the length it takes to normally complete the operation. Its almost like as if it doesn't actually kill the operation tell its over.

Any way adding new yad version of the script. I fined yad to be much better then zenity. To use the script make sure you have yad installed from synaptic.
(If you can fix the error on zenity it will most likely work on yad there very similar.)

[glamdring]

Dose any one know how to gather the information from a check box? For example:

Code: [Select]

yad --title="$TITLE" --form \
--field="check box 2:CHK" TRUE \
--field="Check box 1:CHK" TRUE \

or even a way to gather the information for a check list --list --checklist?

[Neal ManBear]

Have a look at lxcursor.

[glamdring]

Is there a way to have the script jump from one line to another and begin again from there if a criteria is met? For example if [ "$?" = "1" ] go to line 23 fi

[Neal ManBear]

 That would be an if then statement: if this then that.

[glamdring]

I i know/understand that but I mean what would be the command to jump from from one spot in the script to another.

For example:


if
the command to skip from line 21 to 110
fi
21: This part will create folder testing



110: This line will copy files into folder testing

Now I know thats not a great example but what if for some reason I want to jump to line 110 and skip everything in between.

[Neal ManBear]

You mean something like --
if [script == 1] then continue
if [script == 2] then go to line 110

The if then option is pretty flexible. Have you looked at the lusbc script?

[Neal ManBear]

Here is an example of if then from lomanager (in development [by pinoc]) --

Code: [Select]

# check for kdesu or gksu and setup/or run XUGOO
#=================================================
if [ ! -e $XUGOO ];then
  if [ -r /usr/bin/gksu ]; then WMSUDO=/usr/bin/gksu; fi
  if [ -r /usr/lib/kde4/libexec/kdesu ]; then WMSUDO=/usr/lib/kde4/libexec/kdesu; fi
  # setup XUGOO
  echo "#"'!/bin/bash' > $XUGOO
  if [ "$UID" != "0" ]; then echo $WMSUDO lomanager >> $XUGOO; else echo lomanager >> $XUGOO; fi
  chmod a+x $XUGOO
  $XUGOO &
  exit 0
fi

[Neal ManBear]

Look at the script in this thread. It has another example of using if then.