Windows Terminal and @SELECT

[Joe Caverly]

     _x64: 1
   _admin: 1
_elevated: 0

TCC  26.01.40 x64   Windows 10 [Version 10.0.18362.900]

When I run the .BTM from Open UWP apps from the command line on Windows 10 in TCC under Windows Terminal;

...no @SELECT pops up, and the code launches the first option, Alarm_Clocks.

Running TCC outside of Windows Terminal, or in TCMD, it works as it should.

Joe

 

[vefatica]

Here @SELECT, without your BTM, works OK from TCC in Terminal.

 

[vefatica]

It's OK using CLIP: too.

And your BTM seems OK from terminal. I can't launch most things because I don't have them. But I did successfully launch terminal and maps from @SELECT.

 

[Joe Caverly]

Here's what I get running @SELECT from Windows Terminal via TCC;

e:\utils>echo %@select[clip:,50,100,175,400,Select an option]
Alarm_Clocks

Joe

 

[Joe Caverly]

If I launch the .BTM using TCC-RT from Windows Terminal via TCC, it works as it should.

It might be a setting in my TCMD.INI file, which TCC-RT is not using,

However, I don't understand what could be affecting it.

Joe

 

[rconn]

Not reproducible here. Try disabling your TCMD.INI when starting TCC and see if that affects the behavior.

 

[Joe Caverly]

Hey @rconn , yes, it works without the TCMD.INI, which I expected, see (Post #5)

However, since you will not be supporting TCC under Windows Terminal, and @vefatica has shown why it doesn't work, I will look for another solution.

Joe

 

[vefatica]

@vefatica has shown why it doesn't work

I did?

 

[Joe Caverly]

I did?

Well, as you said in the post that I linked to,

When TCC is running in Windows Terminal, it doesn't know where to put the history and dirhistory popups

which is correct, so I'm thinking this is also why the @SELECT does not work.

Which, while you did not specifically indicate @SELECT, it seems in line with my problem.

Joe

 

[vefatica]

Well, as you said in the post that I linked to,which is correct, so I'm thinking this is also why the @SELECT does not work.

Which, while you did not specifically indicate @SELECT, it seems in line with my problem.

Joe

Yeah but @SELECT works OK here even though the dialog shows up in an odd place.

 

[Joe Caverly]

Well, it works in TCC stand-alone, TCC in TCMD, but not TCC in Windows Terminal, unless I start TCC in Windows Terminal without the TCMD.INI file.

In what odd place does the dialog show up on your system?

Joe

 

[vefatica]

Well, it works in TCC stand-alone, TCC in TCMD, but not TCC in Windows Terminal, unless I start TCC in Windows Terminal without the TCMD.INI file.

In what odd place does the dialog show up on your system?

Joe

The coordinates are interpreted relative to the desktop (instead of relative to the console window).

 

[vefatica]

The coordinates are interpreted relative to the desktop (instead of relative to the console window).

Probably not the desktop, but this window (which is returned by GetConsoleWindow().

Module:  C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.0.1811.0_x64__8wekyb3d8bbwe\OpenConsole.exe
Class:   PseudoConsoleWindow
Title:   [none]
Enabled: Yes
Visible: No
Show:    NORMAL
LTRB:    0 0 128 31

 

[vefatica]

Probably not the desktop, but this window (which is returned by GetConsoleWindow().

Module:  C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.0.1811.0_x64__8wekyb3d8bbwe\OpenConsole.exe
Class:   PseudoConsoleWindow
Title:   [none]
Enabled: Yes
Visible: No
Show:    NORMAL
LTRB:    0 0 128 31

Heehee! I can actually move that window around. After

echo %@winapi[user32.dll,MoveWindow,%@eval[0x000F0532],100,100,128,32,0]

it's

Class:   PseudoConsoleWindow
Enabled: Yes
Visible: No
LTRB:    100 100 228 132

And the @SELECT dialog positions itself accordingly.