Release v2.0.0

[BazzaCuda]

Windows 64-bit binaries

Custom Colors

You can now select your own custom color scheme for Custom Menu using three colors:

• background color
• highlight color
• info color

These will effect the color scheme for your custom menus, the Config Dialog and the Icon Explorer.

A new section at the bottom of the Config Dialog allows you to select your colors.
Clicking on one of the three boxes will open the standard Windows Color Selection dialog.

As you experiment with various color schemes, the Config Dialog will immediately change to reflect your color selection.
This includes the editable tree representation of your menus on the left, which will now reflect your color choices for background and highlight.

As well as changing the color of the explanatory text in the Config Dialog and the address bar in the Icon Explorer, the info color also changes the submenu chevron that is displayed in your menus:

Saving your Config Dialog changes will now also save a colors.ini file.
If at any time you get your colors in a complete mess, simply delete colors.ini and relaunch Custom Menu which will revert to the default colors.

As always you can test how your menu will look without leaving the Config Dialog by clicking the Show Menu button. You will have to Save your color changes first. You can click [Esc]ape to subsequently close the menu without selecting one of the menu items. You can then make further changes, save and retest your menu.

You will also have to save your color changes before you seem them reflected in the Icon Explorer.

The Defaults button will reset the colors to their in-built defaults.

CustomMenu.ini Backup
A backup of your CustomMenu.ini file (which stores all your menu data) will be created each time you click Save.

Note
If you restart Explorer.exe without rebooting, you will also need to restart Custom Menu as the handle to your desktop window will have changed and Custom Menu needs to find the details of your new desktop.

Improvements

• You cannot now end up with the Icon Explorer behind the Config Dialog
• the Icon Explorer folder tree won't list archive files as folders
• the Icon Explorer now includes a filter for *.ico files so you have a choice of routes to .ico files via either of the "Select Icon" buttons
• various UI improvements to the Config Dialog and the Icon Explorer

Changes
Don't forget, a right-click on your Custom Menu or any of your submenus will open the Config Dialog
This means, if you still have it in your Custom Menu, you can delete the sample "Right-Click me to open Config" menu item that was created for you when you first ran Custom Menu
This sample menu item is no longer created as some people weren't aware they could delete it and thought they needed it in their main menu as the only way to get into the Config Dialog

---

All feedback is welcome in Discussions.

p.s. I strongly recommend that you only download CustomMenu from my repository here on Github.

---

This discussion was created from the release Release v2.0.0.

[Laurens1964]

Hi Baz,

As soon as I change some things in the menu (e.g. change of submenu name) i get an error.

Don't know how to get around. I've tested it several times and can repeat the error. It is for sure happening when you change the name of a sub-menu or change the name of a menu-item.
It is really helpful that the CustomMenu.ini is automatically backed up. After a crash the original ini-file is losing some information.

Laurens

[BazzaCuda]

Hi Laurens,

Thanks for reporting this. Oddly enough, this bug has been there for some time.
I'm just testing a fix for it now which should be released later today.

Baz.

[BazzaCuda]

Released v2.0.1

It's likely that your CustomMenu.ini file is missing everything following the submenu item.
If so, you will need to copy your most recent CustomMenu.bak file to replace CustomMenu.ini.
(ah, you already said that!)

Baz

[Laurens1964]

The update version is working like a charm. And it seems to be faster as well!
Thanks Baz.

[BazzaCuda]

Excellent news, thanks.
In my haste to release the bug fix I screwed up on the version number built into the exe (2.0.1) and called it 2.0.2 on GitHub. I'll fix that in 2.0.3.