Thats a great app ^^ Thanks for sharing and keep up the good work.
I have stuff to report
- I cant use "telnet"
- it doesnt check the environment variables - i cant use programs in custom folders that are registered in the "path" variable!
There is a bug in the settings:
- Go the the settings menu
- Change the current theme to some other theme
- now change some text effects (i changed the use glass effect)
- press apply theme
- it will request a new name for the theme to save -> deny (click on x on the right top corner)
- now change to another theme and then back
Another thing to note: "exit" doesnt exit the app!
Thanks, and thanks so much for the feedback.
Did Telnet launch and not work, or was it not found in your path?
As for the path/environment variables, Consolium by deafult launches with:
If you launch that, it should behave the same way as Consolium. Maybe you are using a different shortcut for your old console, or your old shortcut starts in a different directory? If you were using a VS2010 shortcut, or some other shortcut that runs an environment script at launch, you would need to adjust your Startup Cmd to be the same. For example, if you have a build/compile window shortcut that loads in a script with all sorts of settings specific to your tools. In Consolium you can create as many shortcuts as you want--with different themes and different launch apps, one for cmd.exe, one for VS2010 cmd.exe, and one for other console apps as well.
Also Consolium doesn't know about your path, or even about what you're typing, it's a pass-through to the underlying console app. Consolium just attaches to the console buffer and renders whatever happens to be in it. Input messages are forwarded to the underlying app.
Thanks for the repro on the settings bug...that is a great help. I'll get that fixed straightaway.
As for exit...for now I at least should pop up a UI block that says, "Use X to Close Consolium" to avoid confusion. Thanks for reminding me. The exit keyword is tricky because Consolium doesn't know what you're typing. Maybe you were exiting an FTP session, or exiting a script. Due to the way I attach to the underlying console and retain it's window handle, its not completely apparent when the process has stopped responding. A good feature to add though.