Yep, blame it on the help file!j_c_hallgren wrote:So that's why as of v111, the Install.exe now is over the 1MB size line! I was wondering when that would occur...the zip is still barely under it...Linkaday wrote:And according to Don's law now scripting commands reference parenthetically grew an overnight horizontal index!
Yep!Linkaday wrote:And according to Don's law now scripting commands reference parenthetically grew an overnight horizontal index!
However, all DOC-2-CHM converters I've tried so far were even worse!For ages I have been putting this information into email messages by pasting in the mapped drive paths, then going to a command window to do a "net use" command so I can copy the \\server\share portion of the UNC to paste over the mapped drive letter(s) in my email message.v7.00.0002 - 2008-04-02 11:42
+ Menu File | To Clipboard: Added command "Item UNC Path/Name(s)".
Copies the full path/name of all selected Tree or List items, using
the UNC path for items located on a mapped drive. Other items are
copied without change.
Code: Select all
XYplorer Beta Club
v7.00.0046 - 2008-04-22 13:34
+ PFA/POM: Now, command line parameters are supported in XYplorer's
Portable File Assocations!
The syntax is identical to all the other places where command line
parameters are supported: Catalog (Open Selected Item(s) With),
UDC Open With, scripting "openwith". It's basically one simple
rule: The application must be quoted when command line parameters
are used. Thank you for pushing me to add the params and telling me how to do it!jacky wrote:Well...Yeah, I love it!Code: Select all
v7.00.0046 - 2008-04-22 13:34 + PFA/POM: Now, command line parameters are supported in XYplorer's Portable File Assocations! The syntax is identical to all the other places where command line parameters are supported: Catalog (Open Selected Item(s) With), UDC Open With, scripting "openwith". It's basically one simple rule: The application must be quoted when command line parameters are used.
Very cool, thanks for this!
The POM is a real highlight for me and my workstyle, one of XY's top features. v7.00.0050 - 2008-04-24 12:23
+ Scripting command enhanced:
- Rename
Now, you can directly state the item(s) to be renamed in the new
argument "itemlist".
Syntax: rename [mode (bat|re|sr|kc|ext)], pattern, [preview (p)],
[itemlist]
itemlist: |-separated list of items (full path) to rename.
If empty then current list selections are renamed.
The | (pipe) resp. the items may be surrounded by
any number of blanks.
Examples:
- Rename a specific file to a hardcoded new name, using itemlist
and the /e switch (for renaming the extension as well):
::rename , "africa.png /e", p,
"E:\TestFiles\asia.jpg"
- Using itemlist you can rename items distributed over completely
different locations using a shared increment. For what it's
worth, the following script...
::rename , New-<#001>, p,
"D:\Download\ss024.jpg |
E:\TestFiles\xxopöä.tif"
... will rename:
ss024.jpg to New-001.jpg
xxopöä.tif to New-002.tif
I think it's more than a personal triumph - evidence of a very special dedication that hardly has it's fellow!Code:
v7.10.0010 - 2008-05-14 11:29
+ Font Preview: Now the Edit box containing the sample text supports
UNICODE. In other words: I finally managed to write a UNICODE
compliant Edit Control -- a personal triumph
WOW, nice to hear that!Linkaday wrote:Underground engineering (unicode thicket, getting rid of user controls ...) bears a not promoted wonderful fruit!
Since 7.10.0040 i'm enjoying another significant reduction of loading time!
Though it's not that eye-catching with XY on a fast fixed disk, but on my USBs it sticks out a mile!
Mounted to any of those relatively slow going environments here at work first startup takes about just half of the time, second even another half of that - an overall reduction to a third of drawing time before!
Though being not that much of a speed freak - this makes having to change hosting machines quite often a day drastically less frustrating
And there are still 2 UCs in... I'd expect another speed increase if they are all gone, and a dramatic memory usage reduction... (this will happen right after 7.20 is published).The parser got better. Now, with full support for expression nesting (parentheses), we are not very far from functions anymore...TheQwerty wrote:Thanks for giving scripting some real logic to replace the string manipulation conditionals!
I've been busy and thus haven't budged since v7.60.0003 - but after thread-crapping in jacky's Automatic Update Thread I didn't want to seem ungrateful. I'm looking forward to updating my scripts and getting a chance to fully test it!