From: David Pirotte <david@altosw.be>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: gtk-menu-popup [guile-gnome2 2.16.1-4]
Date: Tue, 29 Jun 2010 11:42:35 -0300 [thread overview]
Message-ID: <20100629114235.16a07bb7@rascar> (raw)
In-Reply-To: <m3r5jqw3x0.fsf@unquote.localdomain>
Hi Andy,
Thank you! It's working!
What confused me is that the doc @
http://www.gnu.org/software/guile-gnome/docs/gtk/html/GtkMenu.html#GtkMenu
[which I [re]red before to write to the list] is partially correct because the
argument list in the function def is correct [but I didn't catch that as they are
all on one line, I guess], where as the explanation of each argument below
the function def still mention 'data' [which I did red well because they on separate
lines ... :-)]
Cheers,
David
did you see my message about get-path-at-pos?
;; --
— Function: gtk-menu-popup (self <gtk-menu>) (parent_menu_shell <gtk-widget>)
(parent_menu_item <gtk-widget>) (menu_position_func scm) (button unsigned-int)
(activate_time unsigned-int32) — Method: popup
Displays a menu and makes it available for selection. Applications can use this
function to display context-sensitive menus, and will typically supply ‘#f’ for
the parent-menu-shell, parent-menu-item, func and data parameters. The default
menu positioning function will position the menu at the current mouse cursor
position.
The button parameter should be the mouse button pressed to initiate the menu
popup. If the menu popup was initiated by something other than a mouse button
press, such as a mouse button release or a keypress, button should be 0.
The activate-time parameter should be the time stamp of the event that initiated
the popup. If such an event is not available, use gtk-get-current-event-time
instead.
menu
a <gtk-menu>.
parent-menu-shell
the menu shell containing the triggering menu item, or ‘#f’
parent-menu-item
the menu item whose activation triggered the popup, or ‘#f’
func
a user supplied function used to position the menu, or ‘#f’
data
user supplied data to be passed to func.
button
the mouse button which was pressed to initiate the event.
activate-time
the time at which the activation event occurred.
;; --
Le Tue, 29 Jun 2010 12:04:27 +0200,
Andy Wingo <wingo@pobox.com> a écrit :
> Hi David,
>
> On Mon 28 Jun 2010 21:15, David Pirotte <david@altosw.be> writes:
>
> > (gtk-menu-popup popup-menu
> > #f ;; parent-menu-shell or #f
> > #f ;; parent-menu-item or #f
> > #f ;; user supplied func to position the menu
> > or #f #f ;; user supplied data to pass to func
> > button
> > time)
>
> This function did change API when going from guile-gnome-0 to
> guile-gnome-2. I paste below the commit that re-added gtk-menu-popup to
> guile-gnome-gtk. As you can see the prototype is different -- no user
> data to the positioning function.
>
> Cheers,
> Andy
> ...
next prev parent reply other threads:[~2010-06-29 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 19:15 gtk-menu-popup [guile-gnome2 2.16.1-4] David Pirotte
2010-06-29 10:04 ` Andy Wingo
2010-06-29 14:42 ` David Pirotte [this message]
2010-07-01 10:49 ` Andy Wingo
2010-07-02 3:37 ` David Pirotte
2010-07-08 10:51 ` Andy Wingo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100629114235.16a07bb7@rascar \
--to=david@altosw.be \
--cc=guile-user@gnu.org \
--cc=wingo@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).