I have created an AppBar. The AppBar always stays on top, when it loses focus, then to get back to the AppBar requires two clicks instead of one. I believe the first click activates the form and then with second click I receive the mouse click events (as expected). Can you give any ideas, what can be wrong here? My problem is similar to this one Appbar and focus issues[^]. Unfortunately the OP in that link hasn't posted his solution :(. I created the AppBar following this article from CodeProject C# does Shell, Part 3[^] I looked into it with Spy++ but don't have any idea why this is happening. Here is the Spy++ log which I obtained testing out this scenario (first click doesn't works, second does).

<00001> 00090CFE S WM_PARENTNOTIFY fwEvent:WM_LBUTTONDOWN xPos:25 yPos:17
<00002> 00090CFE R WM_PARENTNOTIFY
<00003> 00090CFE S WM_WINDOWPOSCHANGING lpwp:0418EAE4
<00004> 00090CFE R WM_WINDOWPOSCHANGING
<00005> 00090CFE S WM_ACTIVATEAPP fActive:True dwThreadID:00000000
<00006> 00090CFE R WM_ACTIVATEAPP
<00007> 00090CFE S WM_NCACTIVATE fActive:True
<00008> 00090CFE R WM_NCACTIVATE
<00009> 00090CFE S WM_ACTIVATE fActive:WA_CLICKACTIVE fMinimized:False hwndPrevious:(null)
<00010> 00090CFE S WM_IME_SETCONTEXT fSet:1 iShow:C000000F
<00011> 00090CFE S WM_IME_NOTIFY dwCommand:IMN_OPENSTATUSWINDOW dwCommand:00000002 dwData:00000000
<00012> 00090CFE R WM_IME_NOTIFY
<00013> 00090CFE R WM_IME_SETCONTEXT
<00014> 00090CFE S WM_SETFOCUS hwndLoseFocus:(null)
<00015> 00090CFE R WM_SETFOCUS
<00016> 00090CFE R WM_ACTIVATE

Now happens the second click (which works)
<00017> 00090CFE S WM_PARENTNOTIFY fwEvent:WM_LBUTTONDOWN xPos:25 yPos:17
<00018> 00090CFE R WM_PARENTNOTIFY
<00019> 00090CFE S WM_WINDOWPOSCHANGING lpwp:0418E40C
<00020> 00090CFE R WM_WINDOWPOSCHANGING

Looking at the Spy++ logs, I believe the problem is with activation, I think that it only receives WM_LBUTTONDOWN event if the window is activated. But how come other windows aren't activated but they still work with one click (i.e. I don't have to click it first). **EDIT:**I think the problem

I'm using the IAXClient[^] library in CodeProject. The problem is when I debug it, I sometimes get heap corruption errors or sometimes it doesn't registers with the server. It works completely fine in Release builds and in my colleagues PC (checked on three machines, worked fine there), but doesn't on mine. Way back earlier, it worked fine, but that time it didn't run properly outside VS (i.e. I had to run from inside VS otherwise would get heap corruption errors). This is the exception I get while debugging in VS

Windows has triggered a breakpoint in SharpIAX.exe.

This may be due to a corruption of the heap, which indicates a bug in SharpIAX.exe or any of the DLLs it has loaded.

This may also be due to the user pressing F12 while SharpIAX.exe has focus.

The output window may have more diagnostic information.

The call stack looks something like this

> ntdll.dll!7c90120e()
[Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]
ntdll.dll!7c96e139()
ntdll.dll!7c96e576()
ntdll.dll!7c96f75e()
ntdll.dll!7c94bc4c()
ntdll.dll!7c927573()
msvcrt.dll!77c2c2de()
iaxclient.dll!037b8d61()
iaxclient.dll!037b9029()

The fact that it works fine on other machines means that the code may be fine and the problem is with my system or so. And now I want to debug the cause? Any clues? I'm using XP SP3, VS 2008 TE **EDIT:**Found this message on the Output window of VS HEAP[SharpIAX.exe]: Invalid Address specified to RtlFreeHeap( 003C0000, 01389A5C )

modified on Wednesday, June 16, 2010 2:27 AM