Comment 15 for bug 1807022

Wayne

Thanks for that. I wasn't aware there wasn't a unicode option in the edit control so I hadn't tried it. Yes it does seem to exclude WxWidgets.

Inserting the unicode character does not cause a hard crash so it might be a more manageable problem to solve. At a minimum, it is a serious bug. Best case it is a different facet of the same bug.

The fact I *always* get the aforementioned error

"../wxWidgets-3.0.4/src/msw/toplevel.cpp(1545): assert "m_menuDepth > 0 failed in DoSendMenuOpenCloseEvent(): No open Menus?
Do you want to stop the program?"

when I insert an unicode character is probably diagnostic. This should never happen.

I also get a hard crash when I navigate away from insert unicode character and I believe I have seen the error message flash at least a couple times doing that. After all, both are closing the list of unicode characters.

Back tracking from that point might provide a clue. (i.e. we know *why* that error occurs due to !popup and wxEVT_MENU_CLOSE being true). So we are trying to close without isPopup being in the proper state. In other words in wxTopLevelWindowMSW::HandleExitMenuLoop(WXWORD isPopup), isPopup is somehow in the wrong state.

I'd normally try to trace this back to figure out why isPopup is wrong or at least to be sure both hard and soft crashes are the same issue.

I don't know how to make a debug version of WxWidgets for MSW and use it for my Kicad build as I might be able to track back from there. Mind you that would mean learning how to use GDB from the command line but I've love to try.

Sorry for my "amateur hour" type approach. It has worked in the past for me. As a hardware guy I end to work back from the observed failure.