Tuesday, January 29, 2008

v6.80.0045 - 2008-01-29 10:08

  • + Script files now support comments: Each line starting with // is treated as comment (= ignored by the script).

  • + Script files now support continuation of a script over several lines: Simply have any number of blanks at the beginning of a line, and it will be appended (after trimming the blanks) to the previous line.
    Example for a script file:
    -----------------------------------------------------------------
    // here's a dummy script file showing some possibilities
    // =====================================================
    // (1) comment lines start with //
    // (2) a script may run over many lines: A line beginning with
    //      one or more blanks is appended to the previous line,
    //      with one blank auto-inserted between them
    // (3) empty lines are always welcome:

    //goto Desktop, sort by Modified
    Desktop, Modified
      // remove any visual filter (indented comments work as well)
      ::goto Desktop
      ::sortby m, d
    // this is a menu separator:
    -
    // various test scripts
    Copy Blah::copytext Blah
    Copy Blah (2 lines)::copytext Blah <br> Blah
    Copy Blah (2 longer lines)
      // set " # " as line breaker, just for fun
      ::br " # "
      // change argument separator to allow commas in text!
      ::sep /
      ::copytext Blah # Blah
        // larger indents are no problem!
        and this text goes on and on, and the lines do not have to end
        with a blank to avoid that the words will clutch together on
        appending: one blank is auto-inserted between appended lines!
    // load the same file again; pointless but possible :)
    // no menu caption = no problem
    ::loadscriptfile testscripts.txt
    -
    // add a caption without a script to have a clickable
    // menu item without any function
    Cancel
    -----------------------------------------------------------------


  • * Rename Special Batch Rename. Before: "The original file extensions are preserved if the pattern contains no extension." Now: "The original file extensions remain unchanged." Always. Always? No, there's a switch now: If you really want to batch-change your extensions as well, append a "/e" to your pattern!
    Examples:
           Original name: test.txt
      *-<myyyymmdd>       test-20070607.txt
      *-<myyyymmdd>.htm   test-20070607.htm.txt
      *-<myyyymmdd>/e     test-20070607
      *-<myyyymmdd>.htm/e test-20070607.htm
      New<#01>            New01.txt
      New<#01>/e          New01
      New<#01>.csv        New01.csv.txt
      New<#01>.csv/e      New01.csv
    As you see, the /e switch simply means: drop the original extension. Then it depends on the pattern whether a new extension is supplied or not. But wait a minute! Now here's an interesting side effect of the new rules:
           Original name: test.txt
      ping.png/e          ping.png
    See? You can hard-replace the old name completely! And if a file ping.png already exists? Then the collision is auto-avoided like this:
           Original name: test.txt; ping.png exists
      ping.png/e          ping-01.png
    Not bad! BTW, the format of -01 depends on your settings in Configuration Report Number Suffix.