This console application is an exploration of fasm2/fasmg techniques to simplify common patterns by inventing syntax. This includes an extension to the MS COFF support, GLOBSTR extension for VT100/ANSI output/buildup.

This shows effective use of the modern virtual terminal interface in windows. As with most code it's messy and incomplete, with minor testing.

Looks like a very sophisticated tool!

I have link error: [SOLVED]


I need to use x64 Native Tools Command Prompt for VS 2022 instead of "x86" one.

It looks like ENABLE_VIRTUAL_TERMINAL_PROCESSING is not enabled. I am going to experiment with it.

Perfect, it is fun playing with your "console event discovery", I especially like the mouse wheeled event.

In hindsight there are quite a few errors, and comment mistakes. Earlier Windows versions can link against kernel32.lib. Should work on Windows 10 version 1511 (November 2015 update) and Windows Server 2016.

For example, look at how the mouse button events work. Multiple buttons work in a strange way.

I updated your attachment to not include the executable file - please package only the sources whenever possible.

Yes, I tested, it came up "button: 1R" or "button: 12".... but mouse button is not designed to use that way, so I think should be okay.

I don't know what happens to PAUSE command to PowerShell, now it is "Press Enter to continue". Even PAUSE command in CMD does not accept key like Ctrl, Alt, Win.... (Sorry, this is more related to my "keypress" example two days ago. )

MOUSE_EVENT is just a bad design, imho. The button up event could indicate what button has been released. This isn't just about supporting a more complex usage of devices. More about not needing to cache state to respond to the event - the design assumes too much about the usage.

Some of this event handling will be deprecated in future Windows perhaps. Standard Win32 functions can be used for non-terminal UI elements - focusing the terminal on character only features.

Is EVAL necessary here? The only thing that comes to mind is that it strips the function name of the namespace context, but you could also work around it by using &line& idiom in your interceptor. And this should work fine:

That line goes way back - probably the first thing I tried to do in fasmg. bappend works well - I've never used it before.

The example has been updated with the changes from the thread, as well as processing for the keyboard event. Some important oddities of working with events:

• FOCUS_EVENT can be received AFTER event causing console to gain focus!
  
• mouse wheel change is undocumented, [.MouseEvent.dwButtonState] >> 4
  
• [.MouseEvent.dwControlKeyState] is documented incorrectly (partial flags compared to: [.KeyEvent.dwControlKeyState])
  
• PowerShell requires a linefeed to update the prompt.