Take Command / TCMD/LE / TCC/LE Version 10 build 55 uploaded

[rconn]

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

* Fixed a problem with the Windows Installer that resulted in empty installation directories on a few systems.

* CALL - fixed a compatibility issue with CMD when using a variable for the CALL destination.

* PDIR - added support for embedding quoted strings in a PDIR format string (which allows appending arguments with no intervening whitespace, or specifying custom delimiters)

* Added DelayedExpansion directive to the OPTION Startup page.

* Help and Quick Help updates.

 

[vefatica]

On Fri, 20 Feb 2009 21:23:58 -0600, rconn <> wrote:

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

The size of TCC's history and dirhistory popups is still only remembered if you
make it bigger. If you make it smaller, the size is not remembered (in the
current session or subsequent ones).
--
- Vince

 

[rconn]

vefatica wrote:

> On Fri, 20 Feb 2009 21:23:58 -0600, rconn <> wrote:
>
> ---Quote---
>> I've uploaded build 55 to the web and ftp sites.
> ---End Quote---
> The size of TCC's history and dirhistory popups is still only remembered if you
> make it bigger. If you make it smaller, the size is not remembered (in the
> current session or subsequent ones).

WAD (for several technical reasons).

Rex Conn
JP Software

 

[vefatica]

On Sat, 21 Feb 2009 08:16:00 -0600, rconn <> wrote:

>---Quote---
>> The size of TCC's history and dirhistory popups is still only remembered if you
>> make it bigger. If you make it smaller, the size is not remembered (in the
>> current session or subsequent ones).
>---End Quote---

>WAD (for several technical reasons).

Is that "working as designed" or "working as desired"? Either way that behavior
is absolutely unprecedented in my experience and seems, on basic principles,
wrong. Just for kicks I made the popups huge (much bigger than desired). How
am I to make them smaller ... edit the INI file? Will you elaborate on those
technical reasons?
--
- Vince

 

[Steve Fabian]

rconn wrote:
| I've uploaded build 55 to the web and ftp sites.

I've tried several times to download from the ftp site, but either the IFTP
command times out, or the COPY results in truncated files and error messages
for every file like the sample below:

TCC: 450 Transfer aborted. Link to file server lost. "/tcmdle/tcmdle.exe"

This has been the case often in the past several days.
--
Steve

 

[rconn]

Steve Fábián wrote:

> rconn wrote:
> | I've uploaded build 55 to the web and ftp sites.
>
> I've tried several times to download from the ftp site, but either the IFTP
> command times out, or the COPY results in truncated files and error messages
> for every file like the sample below:
>
> TCC: 450 Transfer aborted. Link to file server lost. "/tcmdle/tcmdle.exe"
>
> This has been the case often in the past several days.

Not reproducible here (or reported by anybody else). This is likely to
be either a problem with your ISP or local to your system.

Rex Conn
JP Software

 

[rconn]

vefatica wrote:

> On Sat, 21 Feb 2009 08:16:00 -0600, rconn <> wrote:
>
> ---Quote---
>> ---Quote---
>>> The size of TCC's history and dirhistory popups is still only remembered if you
>>> make it bigger. If you make it smaller, the size is not remembered (in the
>>> current session or subsequent ones).
>> ---End Quote---
> ---End Quote---
>
> ---Quote---
>> WAD (for several technical reasons).
> ---End Quote---
> Is that "working as designed" or "working as desired"? Either way that behavior
> is absolutely unprecedented in my experience and seems, on basic principles,
> wrong. Just for kicks I made the popups huge (much bigger than desired). How
> am I to make them smaller ... edit the INI file? Will you elaborate on those
> technical reasons?

This was discussed at length during the private beta.

Rex Conn
JP Software

 

[vefatica]

On Sat, 21 Feb 2009 15:01:57 -0600, rconn <> wrote:

>> ---Quote---
>>> WAD (for several technical reasons).
>> ---End Quote---
>> Is that "working as designed" or "working as desired"? Either way that behavior
>> is absolutely unprecedented in my experience and seems, on basic principles,
>> wrong. Just for kicks I made the popups huge (much bigger than desired). How
>> am I to make them smaller ... edit the INI file? Will you elaborate on those
>> technical reasons?
>---End Quote---
>This was discussed at length during the private beta.

I remember so mention of the size being saved only when the window was made
larger and I just re-read all I could find (searching the beta forum for
"popup") and found no mention. The behavior makes absolutely no sense; in fact
it seems downright ridiculous (am I alone here?). How is one to make a smaller
size remembered? Editing the INI file works and causes no apparent harm. Why
can't the settings be saved in any event?
--
- Vince

 

[rconn]

vefatica wrote:

> On Sat, 21 Feb 2009 15:01:57 -0600, rconn <> wrote:
>
>
>
> ---Quote---
>>> ---Quote---
>>>> WAD (for several technical reasons).
>>> ---End Quote---
>>> Is that "working as designed" or "working as desired"? Either way that behavior
>>> is absolutely unprecedented in my experience and seems, on basic principles,
>>> wrong. Just for kicks I made the popups huge (much bigger than desired). How
>>> am I to make them smaller ... edit the INI file? Will you elaborate on those
>>> technical reasons?
>> ---End Quote---
>> This was discussed at length during the private beta.
> ---End Quote---
> I remember so mention of the size being saved only when the window was made
> larger and I just re-read all I could find (searching the beta forum for
> "popup") and found no mention. The behavior makes absolutely no sense; in fact
> it seems downright ridiculous (am I alone here?). How is one to make a smaller
> size remembered? Editing the INI file works and causes no apparent harm. Why
> can't the settings be saved in any event?

The problem is that there are two possible formats for window sizes
(row/column and pixel) and the parser can't automagically guess which
one you want when the size is reduced.

I could drop the old syntax, which would simplify everything greatly
from my end but force everybody to edit their TCMD.INI files. (If you
recall, I tried that during the beta and was forced to put it back.)

Rex Conn
JP Software

p.s.: Since you've NEVER been able to resize a 4NT / TCC popup window
for the past 15 years, I'm unsure why the inability to reduce the size
is so disturbing to you today!

 

[vefatica]

On Sat, 21 Feb 2009 16:51:57 -0600, rconn <> wrote:

>> I remember so mention of the size being saved only when the window was made
>> larger and I just re-read all I could find (searching the beta forum for
>> "popup") and found no mention. The behavior makes absolutely no sense; in fact
>> it seems downright ridiculous (am I alone here?). How is one to make a smaller
>> size remembered? Editing the INI file works and causes no apparent harm. Why
>> can't the settings be saved in any event?

>The problem is that there are two possible formats for window sizes
>(row/column and pixel) and the parser can't automagically guess which
>one you want when the size is reduced.

Huh? ... the same way it "guesses" when I make it bigger. What's the
difference.

And I'm not using any syntax. I'm resizing the popup window with the mouse.

>I could drop the old syntax, which would simplify everything greatly
>from my end but force everybody to edit their TCMD.INI files. (If you
>recall, I tried that during the beta and was forced to put it back.)

I haven't followed closely, but hasn't it been established lately that it's now
pixels? You could get rid of the row/column syntax and folks could simply
resize the popup (with the mouse, larger or smaller) and have the new info saved
in the INI file.

I still don't get what the difference is ... making it larger or smaller ...
it's all the same ... new size/placement, save it.
--
- Vince

 

[Jay Sage]

> The behavior makes absolutely no sense; in fact it
> seems downright ridiculous (am I alone here?). How is
> one to make a smaller size remembered?

Vince, you're not alone. This does, indeed, seem ridiculous. It means
that one cannot temporarily enlarge the window and then return to the
previous size.

If editing the INI file is the only way to fix the size, then something
should be included in the options configuration.

-- Jay

 

[Charles Dye]

The problem is that there are two possible formats for window sizes
(row/column and pixel) and the parser can't automagically guess which
one you want when the size is reduced.

I could drop the old syntax, which would simplify everything greatly
from my end but force everybody to edit their TCMD.INI files. (If you
recall, I tried that during the beta and was forced to put it back.)

Or have two sets of directives, the old ones supporting row/column for backward compatibility, and new directives which accept only pixel coordinates/sizes. New directives override old ones; updated size and position written to the new directives (only) on popup close. Clumsy and redundant, but not too difficult to implement, I think.

Or (guessing at your future plans here): Store pixel coordinates/sizes in the registry. If the relevant registry entries don't exist, get values from the .INI file, translate row/column sizes to pixels if appropriate, make up new position from reasonable defaults, and stash these values in the registry. When a popup window is closed, save updated position/size in the registry.

 

[samintz]

I think the bigger issue is that you can make a window bigger, but you
can't reduce it back down without editting the INI file. Although, I
haven't tried it myself. I'm assuming that is the case based on Vince's
description.

-Scott

rconn <> wrote on 02/21/2009 05:51:46 PM:

> The problem is that there are two possible formats for window sizes
> (row/column and pixel) and the parser can't automagically guess which
> one you want when the size is reduced.
>
> I could drop the old syntax, which would simplify everything greatly
> from my end but force everybody to edit their TCMD.INI files. (If you
> recall, I tried that during the beta and was forced to put it back.)
>
> Rex Conn
> JP Software
>
> p.s.: Since you've NEVER been able to resize a 4NT / TCC popup window
> for the past 15 years, I'm unsure why the inability to reduce the size
> is so disturbing to you today!
>
>
>
>

 

[Peter Bratton]

* Help and Quick Help updates.

Small Help error - @PYTHON Help page opens with "@PERL[expression]" instead of "@PYTHON[expression]". "f_python.htm"
--
Peter