Hello Bram,

Now we don't need to access any other field, we can change this when we need to 
access them. The attachment is the patch to rename the variable and fix the 
problem. 

Regards,
Hong Xu
2010/12/5


-----Original Message-----
From: Bram Moolenaar
Sent:  2010/12/05 22:47:29
To: H Xu
Cc: vim_dev@googlegroups.com
Subject:  Re: Fedora 13 Gvim popup pops down unless you hold right mouse down?


Hong Xu wrote:

> >> I think I have fixed this problem. The attachment is the patch. The
> >> reason is that when gtk_menu_popup is called, its last parameter is
> >> not passed in the correct time stamp but GDK_CURRENT_TIME. I fixed
> >> this by adding a global varible, which is ugly, I think. Is there a
> >> better way to pass the time stamp?
> >
> > Perhaps we should rename clipboard_event_time to gtk_event_time and move
> > it to globals.h.
> >
> 
> Hi Bram,
> 
> Would it be better if we use a global pointer, whose type is
> "GdkEvent*", to store the event pointer? Then we can get more
> information about the event through this pointer, including the
> event_time -- In the future, we might also need to access other
> varibles in the GdkEvent.

That involves managing allocated memory.  What other fields would we
use?  And can't we use a simple value for them instead of having to make
a copy?

-- 
Engineers understand that their appearance only bothers other people and
therefore it is not worth optimizing.
                                (Scott Adams - The Dilbert principle)

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org        ///
 \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Attachment: gtk_menu.patch
Description: Tag-cf513f8b-cc95-4673-a4c0-ed621434aeba

Reply via email to