Christophe, just wanted to thank you for a great job with Console Z!!! So kudos!!!!
I have one feature request if you could please please please please please do a new version that is 4K ready?
I'm not sure how to share a screen snippet in here but you could imagine all old applications look pretty bad on a 4K screen even when you customize the DPI and it would be most excellent to have console Z showing off as one of the 4K ready kids in the application stack!!! :P
How do I open an issue?
I'm guessing if you have adhered to all the advice in the following article:
Then is there any chance that moving to a better (but not perfect) UI Framework in WPF?
Just want to say that Console Z is an amazing tool and is still usable on 4K screens so I'm not complaining just wishing more for it as I spend 50% of my computing using it.
Resources are located in /Console/res folder.
Icons are located in: fullscreen1xxx.bmp, fullscreen2xxx.bmp, searchxxx.bmp and toolbarxxx.bmp.
xxx indicates the size of icons. Sizes are 16x16, 20x20, 32x32, 40x40, 48x48, 64x64, 80x80.
128x128 is currently unused but my tip: generate icons in 128x128 or 256x256 and then generates other sizes by shrinking from the high size.
You cannot directly create a bmp file with transparency. Create png files and then you can use AlphaConv by Adam Najmanowicz - A 32bit image converter (PNG, BMP & TGA).
It seems like when my computer crashes (and I have to do a resulting hard shut down), the next time I try to open ConsoleZ, a window just briefly opens and closes immediately after. Has anyone ran into this issue?
After 8 months, I think I've tracked down what it was. I think it has to do with the interaction between Console2/Z and my git bash. This SO answer sums up the issue I was seeing, http://stackoverflow.com/questions/18502999/git-extensions-win32-error-487-couldnt-reserve-space-for-cygwins-heap-win32/31970708#31970708. TLDR: Cygwin tried to load DLL into a fixed address that was already used. Returns error.
People, if you really want this bug be fixed you should massively ask about progress here: Microsoft/BashOnWindows#111
It seems Visual Studio Code will use
winpty as workaround.
Microsoft has not planned to fix this bug because too few people has complained and some applications wrote workaround.
If you want Microsoft developers change their mind, show them you care about this bug!
I don't know if workarounds are 100% functional...