This is NOT an "Ask For Help" topic!!!...I posted this in Bug Reports, cuz this is CLEARLY a Bug, it doesn't matter if the bug is in Windows or AutoHotkey, it is a bug!
I am highly offended
by nnnik (or someone) unilaterally MOVING my CLEAR Bug Report out of Bug Reports & into Ask For Help...he didn't leave my topic in Bug Reports for even 1 day!...he just chose, unilaterally, without any other discussions (for example, with LEXIKOS!!!), that "nope, this guy's an idiot, this isn't a bug" & moved it. I want this moved back to Bug Reports, AT LEAST until someone official can determine if this...
- Is an AutoHotkey bug, for example: if AHK is free()'ing (or DestroyMenu()'ing) an hMenu that it shouldn't
- Is a Windows bug that needs reported to Microsoft
- Is not a bug, I'm an idiot & the System Menu SHOULD get corrupted like that (aka "by design")
...I, for one, don't think I'm an idiot, I think this is CLEARLY a bug (& should never have been moved out of the place for bug reports)...& there is nothing my script should have to do to avoid it. I'm not saying that AutoHotkey is at fault, but I DO THINK it might be POSSIBLE to see if MAYBE AutoHotkey can avoid this, even if it might be a bug in Windows.
I recommend making a subforum of Bug Reports for "Windows Bugs" or "Not AutoHotkey Bugs"...IF! (& ONLY IF) this is 100% confirmed (BY LEXIKOS) to NOT BE an AutoHotkey bug
...this may still be an AutoHotkey bug, even if you don't think so, only Lexikos can confirm that...(I think it's possible
that AutoHotkey is FREEING the hMenu on shutdown, so despite
this using DllCall, it might STILL be an AHK bug!)...did you NOTICE
that the corruption only happens on when the AutoHotkey script EXITS???
Bug Reports needs to be split in to 2 or 3 subforums...
- Bug Reports
- New Reports
- Confirmed AutoHotkey Bugs
- Confirmed Windows Bugs
..."New Reports" could either be a subforum of Bug Reports...or they could just be posted to the root Bug Reports forum. Posts in New Reports should NOT BE MOVED
for at least 7 days, giving many people time to see them & reply.
I also think it's very odd, that nnnik, an Admin, quoted my entire post
...isn't that just, bad?...I think everyone should always
quote only what's necessary, only what they are replying to...& if replying to the whole post, quote none of it.
nnnik wrote:AutoHotkey has absolutely nothing to do with how DllCalls work. This is a bug within the WinAPI. AutoHotkey can't fix that.
...that's your opinion, how about we wait for Lexikos (the one writing the code) to determine that?
nnnik wrote:Yeah since this is not the behaviour of AutoHotkey but Windows behaviour.
...unless you wrote the code or asked Lexikos before taking action, I don't believe this. Did you not notice that this bug only happens AFTER AutoHotkey exits? AutoHotkey might be freeing memory at that time & MIGHT be DestroyMenu()'ing on the handle to the other process's menu, so, in fact, it COULD BE an AHK bug, not in DllCall, but in the AHK shutdown routine.
nnnik wrote:This is not a bug within AutoHotkey but one within Windows.
...you DON'T know that...you took one look at my post & moved it within 30 secs of seeing it.
jeeswg: thx for your reply, but despite this having been moved to AFH, this isn't a post that's actually Asking for Help. I encountered this behavior (bug) in a script I was writing, finding it highly odd, I created the minimal test case & came to report the bug...maybe a workaround in Script would be nice, but I'd prefer a fix in AutoHotkey (or Windows).