@keliko: Windows doesn't allow an executable to be both a gui application and a console application: you can either have an app which only has a gui and that detaches immediately from any console it is launched from (thus loosing the connection to stdin/stdout); or you can have an app which always has a console window (but can inherit that console from where it is launched).
Windows executables have a flag in their header which indicates the 'subsystem' the executable should be launched under - LiveCode standalones are built as GUI subsystem apps (as most people don't want a console window appearing when they are launched - there isn't actually any difference between a GUI and CONSOLE subsystem windows executable, they can do identical things both can create and show windows, the only difference is whether they talk to a calling console or not!).
In order to have you standalone act as a console app you need to install the visual studio build tools
https://aka.ms/vs/17/release/vs_BuildTools.exe and then you should be able to launch a 'developer prompt' from the start menu.
You can then use the EDITBIN.EXE tool to change the subsystem:
Code: Select all
EDITBIN /SUBSYSTEM:CONSOLE mylivecodeapp.exe
When you do
From a windows console you should then get interactive input and output as you desire.
Note: Before anyone asks, it is *not* possible to have an executable which decides at runtime whether it should bind to a console or not - Console and GUI subsystem executables are run in different ways, and the OS needs to know which an executable is *before* it is launched.