Re: XYplorer Automatic Updater
Posted: 11 Jul 2011 08:28
thanks a lot for the fix!
Forum for XYplorer Users and Developers
https://www.xyplorer.com/xyfc/
Code: Select all
175 readurl $page, "http://www.xyplorer.com/download.php";
Code: Select all
179 regexreplace $XYAU_new_version, $page, ".+?<b>XYplorer ([0-9]{2}\.[0-9]{2}\.[0-9]{4})</b>.+",
Code: Select all
#.##.#### maybe should be ##.##.####
xyplorer_([0-9]\.[0-9]{2}\.[0-9]{4}) maybe should be xyplorer_([0-9]{2}\.[0-9]{2}\.[0-9]{4})
Some scripting command changes in the last few betas, one of them is responsible.no changes to anything
i think jacky has abandoned us here as his last posting is from July 2011 and he used to be here multiple times daily so we'll likely have to rely on our other current scripters to provide updates and fixes to this.mithrin wrote:It seems jacky hasn't fix the 10 bug for non Beta versions.
Yeah I have this problem as well - sucks. Just haven't got around to reporting it/looking into why it's broken.avsfan wrote:Strange -- my automatic updater has suddenly stopped working (no changes to anything, as far as I know).
The error that it fails with is an error box that states: In order to accomplish the desired operation, you need to have the "library" common-jacky.xys installed -- Please download the script file and put it in the same folder as this script file (c:\bin\XYPlorer\Scripts\).
The curious thing about this is that common-jacky is still in that directory -- no changes...
I can still update manually, but the automatic version is so much more FUN!
Any ideas?
That thread is for Bugs in XY's scripting engine, not for those within user created scripts - so no it shouldn't be posted there.mithrin wrote:I found this Thread called "Scripting Bugs" in Bug Reports. Should this non - loading of library script be reported there?
If so would one of the more senior members do it.
Code: Select all
command $output, $input, $args;Code: Select all
$output = command($input, $args);Code: Select all
v10.90.0102 - 2012-03-14 13:36
+ SC getkey enhanced: Added optional parameter flags.
Syntax: getkey(key, section, [INIfile], [flags])
flags: 1: Use XYplorer's native algorithm.
Notes:
- XYplorer's native algorithm for reading INI values will return
leading TAB characters. The standard Windows algorithm will not.
- XYplorer's native algorithm is optimized for reading hundreds of
keys out of huge INI files. It's not made for picking out single
keys as the getkey() function does. So, performance-wise you
will suffer a bit for the added functionality.
Examples where Year=[TAB]2012:
// returns "2012"
text getkey("Year", "Vacation", "<curpath>\holiday.ini");
// returns "[TAB]2012"
text getkey("Year", "Vacation", "<curpath>\holiday.ini", 1);
...
v10.90.0105 - 2012-03-17 20:19
...
* SC getkey: Removed the optional parameter flags added recently in
v10.90.0102. Instead the function now always behaves as if
flags=1, i.e. leading TAB characters in values are returned and
not cropped.Code: Select all
getkey $output, $key, $section, $INIfile;Code: Select all
getkey($key, $section, $INIfile, $flags);Code: Select all
getkey $output, $key, $section, $INIfile;Code: Select all
$output = getkey($key, $section, $INIFile);It currently is possible to have XY check for non-beta versions, but it only happens on startup.lukescammell wrote:To be perfectly honest, I still believe this is something that should be handled natively in XY anyway. It shouldn't be a separate program like many horrible windows programs do it (Acrobat, Java, I'm looking at you) but a simple option for monthly and weekly checks on non-beta versions would be great, as too would an option for daily when you're running a beta.