-
-
Notifications
You must be signed in to change notification settings - Fork 347
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
CKAN opens a console window when launching from Windows Explorer (or a shortcut) #2193
Comments
When I start ckan from windows explorer it opens a command prompt, then the window to choose a KSP instance. After choosing one, both windows close and open the GUI. |
I don't see this as a problem. And, it's been doing this for as long as I can remember |
Ok, it seems that it's my particular configuration of ConEmu that's highlighted this issue. I can work around it and presumably nobody else is bothered by the temporary console window popping up. |
CKAN Version:
v1.24.0-PRE+0eacb1575574
Operating System:
Windows 10 (64-bit)
The issue you are experiencing:
Double-clicking on 'ckan.exe' (or an equivalent shortcut) opens a Command-prompt before opening the GUI; the Command-prompt persists while the GUI is running.
I can't recall older versions of CKAN exhibiting this behaviour, but I'm not sure when this changed or even if my recollection is faulty in this regard.
Additionally, in my case, I use the "ConEMU" application. This means that when I start CKAN, it jumps to the last active ConEMU window and opens a new tab in that - even if that is on another Virtual Desktop.
It would be very nice if opening up the console could be prevented when launching the CKAN binary from a GUI.
I had a quick play, and changing the CKAN-cmdline application from 'Console Application' to 'Windows Application' does fix it, but unfortunately this completely prevents command-line interaction with ckan so is not an option.
How to recreate this issue:
Double-click on 'ckan.exe' from Windows Explorer
The text was updated successfully, but these errors were encountered: