From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: Eli Zaretskii <eliz@gnu.org>,
stefankangas@gmail.com, 64440@debbugs.gnu.org
Subject: bug#64440: 30.0.50; [PATCH] Highlight on non toolkit menu bar items
Date: Tue, 12 Sep 2023 19:26:20 +0800 [thread overview]
Message-ID: <87wmwv7hur.fsf@yahoo.com> (raw)
In-Reply-To: <87sf7kh1rg.fsf@ledu-giraud.fr> (Manuel Giraud's message of "Mon, 11 Sep 2023 22:51:31 +0200")
Manuel Giraud <manuel@ledu-giraud.fr> writes:
> +#if defined HAVE_WINDOW_SYSTEM && !defined HAVE_EXT_MENU_BAR
> +
> +/* Get information about the menu-bar item at position X/Y on frame F.
> + Return menu-bar's item char position in H_START/H_END and pixel
> + position in X_START/X_END. Value is
> +
> + -1 if X/Y is not on a menu-bar item
> + 0 if X/Y is on the same item that was highlighted before.
> + 1 otherwise. */
> +
> +static int
> +get_menu_bar_item (struct frame *f, int x, int y, int *h_start, int *h_end,
> + int *x_start, int *x_end, int *vpos)
> +{
> + Mouse_HLInfo *hlinfo = MOUSE_HL_INFO (f);
> + struct window *w = XWINDOW (f->menu_bar_window);
> + struct glyph_row *row;
> + int dummy;
> + Lisp_Object items;
> + int i;
> +
> + /* Find glyph's hpos and vpos under X/Y. */
> + if (x_y_to_hpos_vpos (w, x, y, h_start, vpos, NULL, NULL, &dummy) == NULL)
> + return -1;
> +
> + /* We do not support R2L menu bar. */
> + row = MATRIX_ROW (w->current_matrix, *vpos);
> + if (row->reversed_p)
> + return -1;
> +
> + /* Compute h_start and h_end for this menu bar item. */
> + items = FRAME_MENU_BAR_ITEMS (f);
> + for (i = 0; i < ASIZE (items); i += 4)
> + {
> + Lisp_Object pos, string;
> + string = AREF (items, i + 1);
> + pos = AREF (items, i + 3);
> + if (NILP (string))
> + return -1;
> + if (*h_start >= XFIXNUM (pos)
> + && *h_start < XFIXNUM (pos) + SCHARS (string))
> + {
> + *h_start = XFIXNUM (pos);
> + *h_end = *h_start + SCHARS (string);
> + break;
> + }
> + }
> +
> + /* Convert to pixels bounds. */
> + *x_start = 0;
> + for (i = 0; i < *h_start; ++i)
> + *x_start += row->glyphs[TEXT_AREA][i].pixel_width;
> +
> + *x_end = *x_start;
> + for (i = *h_start;
> + CHARPOS (row->glyphs[TEXT_AREA][i]) != -1
> + && i < row->used[TEXT_AREA];
> + ++i)
> + *x_end += row->glyphs[TEXT_AREA][i].pixel_width;
> +
> + /* Is mouse on the highlighted item? */
> + if (EQ (f->menu_bar_window, hlinfo->mouse_face_window)
> + && *vpos >= hlinfo->mouse_face_beg_row
> + && *vpos <= hlinfo->mouse_face_end_row
> + && (*vpos > hlinfo->mouse_face_beg_row
> + || *h_start >= hlinfo->mouse_face_beg_col)
> + && (*vpos < hlinfo->mouse_face_end_row
> + || *h_end < hlinfo->mouse_face_end_col
> + || hlinfo->mouse_face_past_end))
> + return 0;
> +
> + return 1;
> +}
> +
> +/* Possibly highlight a menu-bar item on frame F when mouse moves to
> + menu-bar window-relative coordinates X/Y. Called from
> + note_mouse_highlight. */
> +
> +static void
> +note_menu_bar_highlight (struct frame *f, int x, int y)
> +{
> + Lisp_Object window = f->menu_bar_window;
> + Mouse_HLInfo *hlinfo = MOUSE_HL_INFO (f);
> + int h_start, h_end, vpos, x_start, x_end;
> + int rc;
> +
> + /* Function note_mouse_highlight is called with negative X/Y
> + values when mouse moves outside of the frame. */
> + if (x <= 0 || y <= 0)
> + {
> + clear_mouse_face (hlinfo);
> + return;
> + }
> +
> + h_start = h_end = 0;
> + rc = get_menu_bar_item (f, x, y, &h_start, &h_end, &x_start, &x_end, &vpos);
> + if (rc < 0)
> + {
> + /* Not on menu-bar item. */
> + clear_mouse_face (hlinfo);
> + return;
> + }
> + else if (rc == 0)
> + /* On same menu-bar item as before. */
> + return;
> +
> + if (!NILP (Vmouse_highlight))
> + {
> + /* Record this as the current active region. */
> + hlinfo->mouse_face_beg_col = h_start;
> + hlinfo->mouse_face_beg_row = vpos;
> + hlinfo->mouse_face_beg_x = x_start;
> + hlinfo->mouse_face_past_end = false;
> +
> + hlinfo->mouse_face_end_col = h_end;
> + hlinfo->mouse_face_end_row = vpos;
> + hlinfo->mouse_face_end_x = x_end;
> + hlinfo->mouse_face_window = window;
> + hlinfo->mouse_face_face_id = MENU_FACE_ID;
> +
> + /* Display it as active. */
> + show_mouse_face (hlinfo, DRAW_MOUSE_FACE);
> + }
> +}
> +#endif
> \f
>
> /***********************************************************************
> @@ -35538,6 +35663,16 @@ note_mouse_highlight (struct frame *f, int x, int y)
> w = XWINDOW (window);
> frame_to_window_pixel_xy (w, &x, &y);
>
> +#if defined HAVE_WINDOW_SYSTEM && !defined HAVE_EXT_MENU_BAR
> + /* Handle menu-bar window differently since it doesn't display a
> + buffer. */
> + if (EQ (window, f->menu_bar_window))
> + {
> + note_menu_bar_highlight (f, x, y);
> + return;
> + }
> +#endif
> +
Thanks, but I'd prefer an option to disable this. Additionally, could
you insert the preprocessor condition in a comment after each #endif?
Some of the preprocessor blocks are very long.
next prev parent reply other threads:[~2023-09-12 11:26 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 15:59 bug#64440: 30.0.50; [PATCH] Highlight on non toolkit menu bar items Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-04 16:14 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-01 18:55 ` Stefan Kangas
2023-09-02 0:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-02 6:41 ` Eli Zaretskii
2023-09-02 13:09 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-05 9:53 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-10 7:31 ` Eli Zaretskii
2023-09-10 7:33 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-11 12:32 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-11 13:41 ` Eli Zaretskii
2023-09-11 14:59 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-11 15:58 ` Eli Zaretskii
2023-09-11 18:56 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-11 19:12 ` Eli Zaretskii
2023-09-11 20:51 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-12 11:13 ` Eli Zaretskii
2023-09-12 11:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-09-12 12:48 ` Eli Zaretskii
2023-09-12 13:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-12 13:15 ` Eli Zaretskii
2023-09-12 13:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-12 13:34 ` Eli Zaretskii
2023-09-12 13:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-12 13:56 ` Stefan Kangas
2023-09-12 14:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-12 14:27 ` Stefan Kangas
2023-09-13 16:48 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-06 12:49 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-06 13:14 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-06 15:39 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-06 15:59 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-21 10:19 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-21 10:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-21 11:02 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-21 11:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-21 12:02 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-21 12:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-21 12:44 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-21 12:48 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-21 13:03 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-21 13:24 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-21 13:56 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-27 8:11 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-27 8:18 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-27 10:35 ` Eli Zaretskii
2023-10-28 5:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-29 9:02 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-29 10:18 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-21 11:10 ` Stefan Kangas
2023-10-21 12:06 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-21 10:31 ` Stefan Kangas
2023-09-11 12:51 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-02 13:05 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wmwv7hur.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=64440@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=manuel@ledu-giraud.fr \
--cc=stefankangas@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).