# ReactOS menu fixes address submenu clicks, icon loading, and related bugs

DevFeed: [ReactOS menu fixes address submenu clicks, icon loading, and related bugs](<https://devfeed.tech/articles/menus-menus-32862.md>)

Original publisher: [Read original article](<https://reactos.org/blogs/menus-menus/>)

Published: 2014-03-16T00:00:00Z

Content type: article

Language: en

Sources: [Front Page on ReactOS Website](<https://devfeed.tech/sources/front-page-on-reactos-website.md>)

Topics: [ReactOS](<https://devfeed.tech/topics/reactos.md>), [bug](<https://devfeed.tech/topics/bug.md>), [WINE](<https://devfeed.tech/topics/wine.md>), [Linux](<https://devfeed.tech/topics/linux.md>)

Tags: [bugs](<https://devfeed.tech/tags/bugs.md>), [free](<https://devfeed.tech/tags/free.md>), [icons](<https://devfeed.tech/tags/icons.md>), [issue](<https://devfeed.tech/tags/issue.md>), [linux](<https://devfeed.tech/tags/linux.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [os](<https://devfeed.tech/tags/os.md>), [react](<https://devfeed.tech/tags/react.md>), [reactos](<https://devfeed.tech/tags/reactos.md>), [win32](<https://devfeed.tech/tags/win32.md>), [winapi](<https://devfeed.tech/tags/winapi.md>), [wine](<https://devfeed.tech/tags/wine.md>)

## AI overview

A ReactOS developer describes fixing menu submenu and click behavior, including a workaround for bogus WM_ACTIVATE messages. They also report applying and submitting Wine patches, fixing first-display icon loading, and continuing work on start menu, filebrowser menu, and keyboard navigation bugs.

## Source excerpt

I began the week by fixing the menus, so that they would properly display submenus, and react to clicks. I was stuck for a bit, but I finally managed to find the problem that prevented the menus from working correctly within ReactOS. I set the filebrowser aside for a bit after this small success, to revisit some of the old bugs and pending tasks. I took a fresher look at the exec issue, where items weren't clickable unless a submenu had been opened first, and I (painfully) traced the issue to pointless/bogus WM_ACTIVATE messages, with the new HWND being equal to the old HWND.