11
Help / Re: wxsmith crashes while dragging
« Last post by Wkerry on November 29, 2023, 09:31:13 am »I wonder if "o m l k" is now an AI bot as responses and posts are strange and do not make allot of sense for the last few weeks.
Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!
I suggest next time you post something, you do more research about the topic, this is not the first time you post such nonsense.Explain why it doesn't make sense, it's not a simple solution and I'm not a newbie, so I'll gladly listen to how it should be right in this case.
A wxMouseEvent does not propagate, only wxCommandEvent derived events do, so your proposed change does nothing.
0xaaaaaaaaaaaaaaaa means that the code has accesed freed memory, but I can not see where this may happen. This is the relevant code:Maybe the usage int StopPropagation () would be better?CodeEDIT: Cannot reproduce on MSW, may be MacOS-specific.void wxsItemEditorContent::OnMouse(wxMouseEvent& event)
{
// Anti-recursion lock
static bool IsRunning = false;
if ( IsRunning ) return;
IsRunning = true;
...
IsRunning = false;
}
// Anti-recursion lock
static int recursion_count = 0;
static bool IsRunning = false;
if ( ++recursion_count > 2 ) {
recursion_count = 0;
event.StopPropagation();
return;
}
if ( IsRunning ) return;
-- Build file: "no target" in "no project" (compiler: unknown)--