-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Console attachment logic #30
Comments
This issue has been mentioned on Image.sc Forum. There might be relevant details there: https://forum.image.sc/t/jaunch-a-new-java-launcher-test-fiji-with-java-21/92058/1 |
Tangentially related is this SO post, which talks about the |
What we really need though is to attach contingently to the console, depending on whether one is already active. And only pop a new console when |
Just noting that in 392c60e I set If we do go back to console mode I'm curious, if the // Get the handle to the console window
HWND consoleWindow = GetConsoleWindow();
// Check if the console window handle is valid
if (consoleWindow != NULL) {
// Hide the console window
ShowWindow(consoleWindow, SW_HIDE);
} Also wondering if this needs to be repeated for both the C and kotlin launchers? |
Actually right now when I launch from an existing console Fiji just attaches to it. I'm actually not sure we need any other logic here at all. edit: edit: adding |
Since the |
The ImageJ Launcher has logic to attach to a console using
freopen
with channelsCONIN$
(stdin) andCONOUT$
(stdout and stderr), as well as create a new console usingFreeConsole()
+AllocConsole()
. And it has a hidden option--console
/--attach-console
which callsattach_win_console()
to do this. It also has--new-console
to create a new console. Is this ever actually necessary?The text was updated successfully, but these errors were encountered: