Take Command / TCMD/LE / TCC/LE 11.0 build 46 uploaded

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

rconn

Administrator
Staff member
May 14, 2008
10,100
85
#1
I've uploaded build 46 to the web and ftp sites.


Build 46:
---------
TCC - added checking for keystroke plugins during filename completion,
keyboard block marking, and history recall.

TCC - (Hopefully) Fixed a problem when redirecting output if your code page is UTF-8 or DBCS.

TCC - reinstated support for Regina REXX.

@LINES - fixed a sporadic Windows problem when the file contains
extended ASCII characters (and the file is not Unicode).

DESCRIBE - fixed a sporadic Windows problem when descriptions contain
extended ASCII characters (and the description file is not Unicode).

FOR - added support for batch & environment variables at the beginning
of the FOR command (to set FOR switches). All variables up to the variable immediately preceding "in", are assumed to be in need of expansion before the FOR command is parsed.

TCTOOLBAR - fixed a problem with /U not always correctly updating
TCMD.INI.

Build 45:
---------
LIST - fixed a (Windows) problem with the Print dialog sometimes appearing behind the Take Command window.

TCTOOLBAR - updated docs and fixed a problem when not specifying a tab
title.

UNZIP - fixed an error message when unzipping with /D in a directory
with embedded whitespace.

Help file updates.

Build 44:
---------
TCC - fixed a problem when invoking help from a stand-alone TCC console window.

TCC - fixed a problem with not displaying Windows loader popup errors.

Build 43:
---------
TCMD - fixed a problem when loading a custom console color palette from the registry that doesn't define all 16 colors.

Fixed a Windows IPC bug that caused 32-bit versions of TCC to potentially hang 64-bit versions of Take Command.

Build 42:
---------
TCMD - now detects custom console palettes when attaching an existing console window.
 
May 29, 2008
517
3
Groton, CT
#2
@LINES fails.

I've uploaded build 46 to the web and ftp sites.


Build 46:
---------
TCC - added checking for keystroke plugins during filename completion,
keyboard block marking, and history recall.

TCC - (Hopefully) Fixed a problem when redirecting output if your code page is UTF-8 or DBCS.

TCC - reinstated support for Regina REXX.

@LINES - fixed a sporadic Windows problem when the file contains
extended ASCII characters (and the file is not Unicode).

DESCRIBE - fixed a sporadic Windows problem when descriptions contain
extended ASCII characters (and the description file is not Unicode).

FOR - added support for batch & environment variables at the beginning
of the FOR command (to set FOR switches). All variables up to the variable immediately preceding "in", are assumed to be in need of expansion before the FOR command is parsed.

TCTOOLBAR - fixed a problem with /U not always correctly updating
TCMD.INI.
With this new build, it seems like %@LINES[foo], where foo is the name of any extant file whatsoever returns -1. This is a show-stopper for me.
 
Apr 1, 2010
43
0
#3
Thank you very much for making new build!

After some preliminary test, MBCS(UTF-7(CP65000)/UTF-8(CP65001)/Big5(CP950)) works in DIR and TYPE, more tests will be done later.
 
#9
On Mon, 19 Apr 2010 08:25:23 -0400, rconn <> wrote:

|---Quote---
|> OPTION /U keeps telling me that my software is up to date (It's build
|> 45).
|---End Quote---
|Not reproducible here. I'll pass it on to the installer developers.

Build 47 is OK.
--
- Vince
 

Charles Dye

Super Moderator
Staff member
May 20, 2008
3,383
39
Albuquerque, NM
prospero.unm.edu
#10
I've uploaded build 46 to the web and ftp sites.


Build 46:
---------
TCC - added checking for keystroke plugins during filename completion,
keyboard block marking, and history recall.
It is checking for keystroke plugins, but behaves a little oddly if it finds one. Using a simplified, dummy keystroke procedure:

Code:
{
    if ( ki->nKey != TriggerKey )
        return 0;

    honk();

    ki->nKey = 0;
    return 0;
}
... if the hotkey is pressed during either filename completion or a history search, the routine is called (it beeps) but then the cursor moves a step right and completion/history search is interrupted. Treating a return value of zero as an actual (null) keypress, rather than ignoring it?

Thanks for looking into this!