Re: No refresh of buffer before popup-menu

[Lennart Borgman (gmail)]

Jason Rumney wrote:
> Lennart Borgman (gmail) wrote:
> > Thanks, but is there a global variable wv? Do you mean 
> > current_popup_menu? Is that what is freed in w32_free_menu_strings? 
> > That is called right after discard_menu_item.
> >
> > So I still do not understand.
>
> Indeed it is w32_free_menu_strings that is the function I was thinking 
> of, current_popup_menu is the Windows menu handle, and it seems the data 
> I was thinking of is not stored as global variable but accessible 
> through the menu handle. It is current_popup_menu that is the problem 
> here, when the first menu's strings are being freed, current_popup_menu 
> is actually pointing to the second menu. Looking at the code, we may be 
> able to move things around to avoid this.

Do you mean that the second menu is created before returning from the 
first w32_menu_show. It does not look so to me, but I might be 
misreading the code. Is not "selection" that is returned from the first 
w32_menu_show what is used to decide to do?

Will not the that return value be used to decide what to do (in this 
case popup a second menu)? In popup-menu the return value is used to 
find cmd to execute. So when that is done the first popup menu should be 
gone, or?