Release v1.0.9

Windows 64-bit binaries

• fixed a very minor issue where consecutive right-clicks (or consecutive activations of the menu using the hotkey) without then selecting a menu item to run, resulted in a double-wide menu.

All feedback is welcome in Discussions.

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

Release v1.0.8

Windows 64-bit binaries

• fixed an issue where CustomMenu wasn't recording the Ctrl/Alt/Shift modifiers when the user selected a hotkey. As a result, the modifier combination wasn't being applied the next time CustomMenu was run. If you want to add a Ctrl/Alt/Shift modifier combination to your hotkey, simply delete the contents of the "hotkey" file and relaunch CustomMenu.

All feedback on this new, user-requested mod is welcome in Discussions.

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

Release v1.0.7

Please go to releases for the latest release.

Windows 64-bit binaries

• added an "Open Config Window" menu item to the tray icon.

N.B. CustomMenu treats the entire area above the taskbar as the desktop and any right-click in that area activates the menu. Adding the new menu item encroaches on the desktop area above the taskbar. Consequently, I have reserved the last 30 pixels above the taskbar to accommodate the new menu item; otherwise, left-clicking the menu item would have been treated as a desktop left-click and CustomMenu would have ignored it.

As a result, there is now a 30-pixel strip across the entire screen, just above the taskbar, which won't activate CustomMenu.
However...the added bonus of this is that if you right-click anywhere along this 30-pixel strip, because CustomMenu is now ignoring it, the standard Windows desktop menu will be displayed. Try it out!

#SilverLinings :D

All feedback on this new, user-requested mod is welcome in Discussions.

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

Release v1.0.6

Please go to releases for the latest release.

Windows 64-bit binaries

• Implemented hotkey activation of CustomMenu

To use, simply create a file called "hotkey", with no extension, in the same folder as CustomMenu.exe

When you launch CustomMenu a dialog box will appear so you can choose a combination of keys to use as a hotkey. When you are happy with your combination, click the OK button with your mouse.

Currently, when you press your hotkey or hotkey combination, CustomMenu will appear initially at coordinates (0,0) on your screen, and thereafter at the last place you clicked the desktop while CustomMenu was running. I will release an update shortly to resolve this when I've decided how best to resolve it :P In the meantime, embrace the randomness :D
EDIT: I have updated the v1.0.6 download (see assets) to resolve this. Activating the hotkey now displays CustomMenu in the middle of the screen.

If you want to change your chosen hotkey, either delete and recreate an empty "hotkey" file, or edit the current file and delete its contents.
If you want to stop using a hotkey altogether, simply delete the "hotkey" file.
In all cases you will need to restart CustomMenu.

All feedback on this new, user-requested hotkey facility is welcome in Discussions.

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

Release v1.0.5

Please go to releases for the latest release.

Windows 64-bit binaries.

• Fixed an issue on some Windows10 and Window11 machines which have a slideshow playing on the desktop, or Windows has been set to automatically change the desktop wallpaper at certain intervals. In these scenarios (and possibly others), Windows sends the mouse clicks to a completely different [hidden] window, rather than to the usual, visible desktop. As a result, CustomMenu was ignoring those mouse clicks because it didn't know they should be treated as desktop clicks. Consequently, CustomMenu wasn't appearing. (See the discussion for more info). This now appears to have been addressed. If you have similar issues with CustomMenu not appearing, please let me know in Discussions (https://github.com/BazzaCuda/CustomMenu/discussions).

• The config window now explicitly states that Icon Library files (*.icl files) are supported in the Icon Explorer window.. A new filter has been added to the Icon Explorer window, specifically for *.icl files. Icons for your CustomMenu items can be selected from EXEs, DLLs, CPLs, ICLs, OCXs and DRVs, and probably others.

• EXPERIMENTAL: Currently, CustomMenu responds when you right-click the desktop. If you hold down a CTRL key when you right-click, the normal Windows menu will appear. This behavior can be reversed if you create a file called "ctrl-click", with no extension, in the same folder as CustomMenu.exe: a right-click will bring up the Windows menu as you would expect, and your CustomMenu will appear if you CTRL-rightclick the desktop. There are two things to note:

1. For performance reasons, CustomMenu will only look for the "ctrl-click" file when it starts up, so if you want to try this out, you'll need to exit CustomMenu first and restart it.
2. Normally, when you right-click on the desktop and CustomMenu appears, you can cancel the menu (or a submenu) with a left-click anywhere on the desktop (or press the Escape key). With the "ctrl-click" file present, all operations of CustomMenu will require you to hold down a CTRL key. So, you will need to CTRL-leftclick on the desktop (or press the Escape key) to cancel a menu or submenu, and you will need to CTRL-SHIFT-rightclick to close CustomMenu completely.

Any questions, issues or further suggestions for functionality, please raise them in Discussions (https://github.com/BazzaCuda/CustomMenu/discussions).

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

Release v1.0.4

Please go to releases for the latest release.

Windows 64-bit binaries

Minor tweak

• A minor adjustment to the way CustomMenu determines whether a CTRL/SHIFT/ALT key is down when the desktop is right-clicked, in an attempt to ascertain why on [at least] one Windows 11 machine, right-clicking the desktop activates the normal Windows menu rather than CustomMenu, when CustomMenu is clearly running in the system tray. If you have this issue, please let me know in Discussions as I can't [currently] replicate this problem in my own Windows 11 VM.

EDIT: this issue was traced to the Windows feature of having it automatically change the desktop wallpaper at certain intervals. In this scenario, Windows sends all the mouse movement/click messages to an entirely different [hidden] window than the visible desktop.

CustomMenu_release_v1_0_4.zip

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

Release v1.0.3

Please go to releases for the latest release.

Windows 64-bit binaries

Minor tweaks

1. When pasting an executable's full path into the command edit box any double quotes will be removed. This allows the details to be quickly copied and pasted (unedited) from, for example, SysInternal's Process Explorer or similar applications which always give the full command line with double quotes included.
2. After doing this, if the menu item name is blank or is still the default "New Menu Item", when the menu item name is auto-generated from the contents of the command edit box, the name will be capitalized, which is what most users would do when typing in the menu item's name.
3. Dropping a shortcut (.lnk file) onto the command edit box will also result in the auto-generated menu item name being capitalized.

N.B. point 1 also means that the correct icon will be auto-selected immediately from the executable file. With the opening and closing double quotes still intact, this wasn't happening until the user manually removed the double quotes from the icon file path.

CustomMenu_release_v1_0_3.zip

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

Release v1.0.2

Please go to releases for the latest release.

Windows 64-bit binaries

A very minor tweak. Clicking on the "Feedback" link in the config window goes to the main Discussions page here on Github rather than to a specific discussion. Users can then choose the Discussion for the release they are running and see previous discussions.

CustomMenu_release_v1_0_2.zip

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

Release v1.0.1

Please go to releases for the latest release.

Windows 64-bit binaries.

Removed any references to Windows themes or styles.
Although not being used directly, this may be what is causing an issue in the Config window, with edit box labels not displaying correctly on some machines, with dark text on a dark background.
Can't be 100% sure yet, but they shouldn't be there anyway, so removing them is step 1 in trying to track down the source of the problem.

Edit: This issue currently appears to be isolated to just one person's dev channel Windows 11 computer.

The app's version number is now displayed in the caption of the Config window.

CustomMenu_release_v1_0_1.zip

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

Release v1.0.0

Please go to releases for the latest release.

Windows 64-bit binaries.

Official v1.0.0 release to accompany the release of the source code.

Also fixes the minor memory leak on exit in v0_9_3 when Alt-RightClick has been used to force a re-load of the ini file from disk.

Tested on both Windows 10 and Windows 11, this stable production release is made available to obtain feedback from a wider audience.

Just unzip to a folder of your choice and run.

See the wiki Getting Started page for more details.

All comments and feedback welcome in the discussion section.

CustomMenu_release_v1_0_0.zip

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