Autohotkey script to update automatically your XYplorer beta

[avsfan]

I tried changing the window that it looks for, and it didn't seem to work (i.e. neither of the processes was killed). After looking at the task manager, I think that I know why -- both XY processes show up only as "XYPlorer" in the task list, so if that's the title seen by WinNotExist, it would explain why the rest of the window title doesn't work.

So I looked into the docs a bit, and just added the line

SetTitleMatchMode, 2

above the loop, and all appears to work! So the relevant section now looks like this:

Code: Select all

SetTitleMatchMode, 2

loop, 10
{
IfWinNotExist, XYplorer @
continue ; jumps out of the loop if no more XYplorer left
WinKill
Sleep, 1000 ;waits 1000ms for XYplorer to close
} 

One other question, though: when I hit the key to update, after the update is complete, the AutoHotKey script that I used terminates itself -- is this normal? I looked for any directives that might control this, and couldn't find anything other than "#Persistent" (which is already there)...

Any thoughts?

Thanks again!

andy

[surrender]

A fair question. It's basically just a way to have more tabs open without having them super-crowded. I use one for the various directories that I use in my development environment, and one for the assorted other stuff that I do regularly. I could just pick the folders off the tree, but they're not always where I want them, so I prefer to have a tab for each frequently used folder.

You mean having a second row of tabs would be useful? I personally dont use that many tabs, plus XY's logic is to reduce as many tabs as possible by having tabs like default tab. hmmm but as an option might be useful for multi-tabbers.

Now, I could probably get by with a single XY if it had the "Per-Tab history" that's been discussed before... (after CKS, of course -- but I'd REALLY REALLY love to have each tab have its own history! PLEASE! )

Yeah me too would love to have that. We should bump Don for this after CKS is done.

[lukescammell]

There was some discussion about it here, but... damn, is there anybody who knows how you search this forum and find something???

Here's what I found:

This is when you removed the version number:
http://www.xyplorer.com/xyfc/viewtopic.php?p=1918#1918
Which had explanations on why, and triggered some reactions.

Then, when XY came up, the version number was back.
http://www.xyplorer.com/xyfc/viewtopic.php?p=3694#3694
I don't know it there was a discussion behind this or not, though.

And IMO it's best as it is, with the version number in the filename... I understand the "problem" for automatic procedure, but I think it's best to sort things out, and it's not like XY changes version number (on that level) every day

Thanks for looking it up.

And yes, I share your opinion.

I disagree. In my opinion, you should either name each beta by its full version number, or you should have a single file name that people can update easily from. There's a reason that people like jQuery do exactly that - ease of updating.

http://jquery.com/ <-- look bottom left
http://jquery.com/src/jquery-latest.js
http://jquery.com/src/jquery-latest.pack.js

And then if you want past releases:
http://docs.jquery.com/Downloading_jQue ... oad_jQuery

[admin]

This URL redirects to the URL of the latest BETA (the "noinstall" version) (if I remember to update it on each official release ). It should work with the script (I did not try though).
http://www.xyplorer.com/latestbeta.php

BUT: it might not be such a good idea to automate the BETA upgrading because once in a while there is an important thing to READ in the accompanying change log before you run the BETA...

[lukescammell]

Just need a way of that script automatically showing the last changelog entry and that problem's history...

[noutters]

The url http://www.xyplorer.com/latestbeta.php works fine and I updated the script consequently (1st post of the topic).

[noutters]

the AutoHotKey script that I used terminates itself -- is this normal?

Yes it is normal. The command that kills the script is, guess what, "ExitApp"

[avsfan]

Yes it is normal. The command that kills the script is, guess what, "ExitApp"

Ah, right! I misunderstood and thought that you were calling this script from a hotkey and not just as its own standalone script -- your way is much better for the way I work!

Thanks for the clarification! (and sorry for being a bit brain-dead!)

andy

[noutters]

I updated the script a bit (see first item in the topic).
Changes:
+ Added traytip info about what's going on in the script.
+ Canceling the upgrade deletes the temporary upgrade files and exits the script.
* The script kills only processes called xyplorer.exe (up to 10 instances of xyplorer). That way, no more confusion closing a window that title contains the word "xyplorer".