jey5nd6
jey5nd6
I think it must be something on our side, but I haven't figured out what yet. Here's my modification of the clipboard sample which implements a bunch of it. Doesn't...
OK, I found a couple of differences, but I don't know enough about the samples environment to get it to compile (because it has a bit of Mac-specific code in...
@csomor another difference is that we're running a separate event loop for the dialog with the grid in it: ``` Show( true ); wxGUIEventLoop event_loop; event_loop.Run(); return GetReturnCode(); ``` Might...
@csomor I finally got a reproducible case in the sample. It's not the event loop or the wxGrid stuff; it's the `WDO_ENABLE_DISABLE` (I was passing it the wrong window earlier)....
Well, git tells me the `WDO_ENABLE_DISABLE` was added in 2014, so it's not the freshest code.... However, we do need some sort of disabler as we can't use modal dialogs...
Hmmm..., no, `wxWindowDisabler` has the same problem. Is there some hack we can use to get around this, or some patch we can make to `wxWindow->Disable()` (or the event processing...
Ahh... yes, we only use `WDO_ENABLE_DISABLE` with our "quasi-modal" dialogs (which aren't run with `ShowModal()`).
With the changes we're now getting key events for wxSearchCtrls in our dialogs, which is great. 🎆 However, Cmd-V still doesn't work in search controls that are in the standard...
In the non-wx `NSWindow` case we don't really need the keystroke; we just need the platform to handle it in the native control. For some reason (menu disabling, perhaps?) the...