🚀 go-pugleaf

Keith wrote:
> * Above post refers to settings for your original problem app.
> 
> If you will make this compiler option change, then debug across the prior shown call to SendMessage
> then what you will observe is that while the code generated in your file WinComboBox.cpp doesn't
> change, the action of SendMessageA does, in that the contents of the ESP register are correctly
> updated across the call to SendMessageA, as the four parameters are pitched off of the stack before
> returning control to you in the add() method, whereas with the C-calling convention, the ESP is not
> updated since the four parameters are left on the stack by SendMessageA.
> 
> If, instead of changing the calling convention option, you were to add the following after EVERY
> SendMessage() call (at least in your WinComboBox.cpp file), then it would also work correctly:
> 
> asm {
>        pop ebx
>        pop ebx
>        pop ebx
>        pop ebx
>        }
> 
> So that you would be manually removing the four parameters from the stack.  Hokey?  Somewhat, but not
> really, because it's a machine, and you make it do as you wish.

Thank you.  Changing to stdcall did the trick.  Trying the above 'asm' approach failed.  I 
recieved a 'Access violation at address E816F156.  Read of address FFFFFFFF' error upon 
returning.  Changing to stdcall means that you can't use std::mem_fun for object function 
pointers, interestingly enough.  So more fuel for the fire of those who still write out their 
'for' loops instead of std::for_each.  But it is working.  I'll send you a license key as 
soon as I have updated the web site with the fixed version.

Again, many thanks.

David