SimpleUpdater — Rev. 10.69 / 2016/06/19

[Marco]

Makes sense, the chm file is open and you get a message from Windows that such file is opened and locked. I don't know if checking the status of each file that's going to be updated is worth...

[klownboy]

XYplorer.chm though is probably the key file that would be open that someone may not realize or remember is open whereas most other files associated with XY would be closed since you probably wouldn't be running a copy operation or some other script in the background. Not an issue anyway, I only wanted to follow-up and put the issue to bed.
Thanks,
Ken

[Marco]

Releasing 10.50 for testing.
First script ever to support multilingual support And now configuration file is created upon request even on first run.
Open beta, requires XY 12.10.0001 or greater. Put language file in <xyscripts> folder. As usual, read the comments

[Borut]

SimpleUpdater_Croatian.lng

[admin]

Seeing these scripts inspired me to a little improvement:

Code: Select all

    + Scripting: SCs perm and global now can declare one or more 
      variables and set them in one statement. For example:
        perm $a = "a", $b = "b"; echo "$a, $b"; 

[Marco]

Seeing these scripts inspired me to a little improvement:

Code: Select all

    + Scripting: SCs perm and global now can declare one or more 
      variables and set them in one statement. For example:
        perm $a = "a", $b = "b"; echo "$a, $b"; 

Add also set (ok, rarely used) and unset (more useful). For simmetry

[Marco]

SimpleUpdater_Croatian.lng

Thank you!

[klownboy]

Thanks Don. Not a big deal, but it would also clean up the code quite a lot if we could "unset" multi perms without repeating unset. Marco used unset 13 times in "_Terminate" for Simple Updater v10.50.
Ken

Edit: Marco beat me to it.

[PeterH]

Seeing these scripts inspired me to a little improvement:

Code: Select all

    + Scripting: SCs perm and global now can declare one or more 
      variables and set them in one statement. For example:
        perm $a = "a", $b = "b"; echo "$a, $b"; 

Hey: you fulfilled I wish I didn't even ask for
Thanks a lot

And +1 for klownboys request to allow "unset" for a list of variables.

[Marco]

Just a little personal note: unset is the command that would benefit the most from this addition.
I use perm/global strictly paired with set, because it fits my logic better (conceptually one line per variable), so I would still use perm/global multiple times. But a batch unset is definitely welcome for me.

[admin]

Just a little personal note: unset is the command that would benefit the most from this addition.
I use perm/global strictly paired with set, because it fits my logic better (conceptually one line per variable), so I would still use perm/global multiple times. But a batch unset is definitely welcome for me.

I added that unset thing.

Concerning perm/global: For me the main advantage of the next version is this:

Code: Select all

OLD: perm $strC; $strC = "Kućna strana"; 
NEW: perm $strC = "Kućna strana"; 

[Marco]

[PeterH]

Just a little personal note: unset is the command that would benefit the most from this addition.
I use perm/global strictly paired with set, because it fits my logic better (conceptually one line per variable), so I would still use perm/global multiple times. But a batch unset is definitely welcome for me.

I added that unset thing.

Concerning perm/global: For me the main advantage of the next version is this:

Code: Select all

OLD: perm $strC; $strC = "Kućna strana"; 
NEW: perm $strC = "Kućna strana"; 

To your old: and new: exactly!

For unset an "old:" example:

Code: Select all

"_UnSetDB"
   UnSet $_DB_script; UnSet $_DB;
   UnSet $_DB_cnt; UnSet $_DB_list; UnSet $_DB_tab;
   UnSet $_DB_p; UnSet $_DB_p2;  
   UnSet $_DB_file;

[Marco]

Rev. 10.50 is out!
Read the first post and the changelog for more info.

[Marco]

ENG.png

ITA.png

HRV.png