Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo


#334 fully transparent, console.xml changes not taking effect

Stephen Abrams

I managed to make the window completely invisible. Attempts to change this via the console.xml file do not work. I also tried deleting everything and reinstalling by re-extracting the zip, but presumably something is stored elsewhere storing the configuration.

Windows 7 Pro 64 bit, Console-2.00b145-Beta

Bug is that changes to config.xml do not work in my environment. A nice-to-have would be to not let me shoot myself in the foot by making everythign fully transparent.

(Great app, otherwise!)


  • Kirill


    there is a good chance that you have "%appdata%\console\console.xml" file (quotes are actually needed only if you want to work with this file from cmd.exe).

    If you do, you can change settings/appearance/transparency@active_alpha to 255 in that file. Or you can move that file somewhere to not loose your <tabs>.

    If you happen to have Tray Icon, you can access Edit -> Settings from there too.

    Personally, I don't know how to protect you except suggesting to use my custom build with Tasbar button or Marko's builds with Tray icon.

    Marko, may be we should warn the user on OK in Settings dialog if the transparency is too low and both Tray Icon or Taskbar button are unchecked.


    • priority: 5 --> 6
  • I think the easiest way is to limit the lowest setting to something like 1, 5 or 10, so a user can't make a window completely invisible.

  • Kirill

    Limiting the lowest setting is the easiest. However, it is limiting and I could not choose a limit, that I would be comfortable with.

    If you do go with a limit of, for example, 15, do you think we can reduce the precision as well? Let's say, max = 240, step = 20 (choose values to allow 0 without special cases).

  • Ok, I have limited max window transparency to 250, so it's not possible to make Console window completely invisible (just barely noticable :-)

    The fix will be available in the next build.


    • status: open --> open-fixed