Bug reproduced here. For that matter, in two computers, one with 36.52.88 and another that's still on 36.52.80.

Did you test the AltGr-4 dead key (ã, ñ, õ) as well?

All my keyboards are wired; no Bluetooth whatsoever. This doesn't (ok, shouldn't) have anything to do with it... although I can imagine keyboards with poor firmware having problems with the AltGr layers, but in that case, all applications would be affected, not just TCMD/TCC from 36.50 onwards...

Turns out that that Windows 10 computer already had TCMD 36.50.71, which has distinct results. TCC 36.50.71 (installed within TCMD 36.50.71): TCC 36.50.71 running by itself in a Windows Console Host produces: aa-aa-ȧā-ạα (the dead keys in the base and Shift layers were ignored; the ones in...

With both previous posts in mind, what I meant by: Was simply to open a TCC instance, and then type on the keyboard each of those characters one by one, first dead key and then the "letter a", with hyphens in between each pair "for clarity". I am using the es-IB layout, pictured in the...

Actually, when you press any key, two distinct events are recorded and sent to the computer: a MAKE code (the user pressed the key) and a BREAK code (the user released the key). You can see this in action in the "DOWN" and "UP" messages in the Switch Hitter screenshot. This is how the operating...

Say you want to type a semicolon (';') on a computer keyboard. When you press this key: in a computer keyboard, even in one that doesn't say ";" in its printed legend, what the keyboard actually sends is the scan code that corresponds to that physical key: 0x27 in this example. (in this...

I tried again; things don't work out as expected. Test input: áà-äâ-ȧā-ạα (two characters per layer: base: áà ; Shift: äâ ; AltGr: ȧā ; AltGr-Shift: ạα ) Stand-alone TCC: TCC (.83), inside TCMD (.80), Start in ConPTY: TCC (.83), inside TCMD (.80), Start in a New Tab: The square...

Running them from TCMD 36.52.80: Same behaviour for TCC 36 as before; TCC, Start in ConPTY: no dead keys at all.

This is the same, after renaming away TCMD.INI and TCSTART.BTM (and alias.txt, for good measure). No difference: (base layer: áà ; Shift layer: äâ ; AltGr layer: ā ; AltGr-Shift layer: α)

I reinstalled stand-alone TCC 35.00.21. It works normally. I started a TCC 36 window (dead keys don't work); ran TCC 35 within it ⇒ dead keys do work.

No change. Behaviour is the same as before, both when running TCC.EXE by itself and within TCMD (.80).

I was about to post asking if something like this was happening to anyone else. I have 36.52.80 on two different computers, both running Windows 11 Pro, with the es-IB layout (which has many dead keys). Running TCC.EXE directly, the dead keys (acute accent, diaeresis, etc.) in the base and...

Fri 02-01-26 09:17:28 22424 0 {0} >resolution \\.\DISPLAY1, Intel(R) Iris(R) Xe Graphics Monitor: MONITOR\HAT1330\{4d36e96e-e325-11ce-bfc1-08002be10318}\0006 Refresh rate: 60 Hz Color depth: 32 Screen resolution: 1920 x 1080 Scaling: 150% (DPI 96 x, 96 y)...

Mission-critical, systems code... on a language without a formal specification (and still evolving), and with just one production-grade compiler. This, no matter what programming language has been chosen, is enough to stop that goal dead on its tracks right there. Never mind that "replace the...