public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Hannes Domani <ssbssa@yahoo.de>
To: Hannes Domani via Gdb-patches <gdb-patches@sourceware.org>,
	 Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH 01/22] Initial TUI mouse support
Date: Thu, 11 Mar 2021 17:48:49 +0000 (UTC)	[thread overview]
Message-ID: <610501495.582273.1615484929627@mail.yahoo.com> (raw)
In-Reply-To: <87k0qd7g0i.fsf@tromey.com>

 Am Donnerstag, 11. März 2021, 18:32:32 MEZ hat Tom Tromey <tom@tromey.com> Folgendes geschrieben:

> >>>>> "Hannes" == Hannes Domani via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Hannes> Implements an overridable tui_win_info::click method whose arguments
> Hannes> are the mouse coordinates inside the specific window, and the mouse
> Hannes> button clicked.
>
> Thank you.  This is a very welcome development.
>
> I won't comment on tests or comments in the code.
>
> Hannes> +#ifdef BUTTON5_PRESSED
> Hannes> +        else if (mev.bstate & BUTTON4_PRESSED)
> Hannes> +          wi->backward_scroll (3);
> Hannes> +        else if (mev.bstate & BUTTON5_PRESSED)
> Hannes> +          wi->forward_scroll (3);
> Hannes> +#endif
>
> One question I have here is that, right now, the mouse wheel already
> works to scroll for me.
>
> I assume this won't change.  But I wonder why new code is needed.
> Maybe it's the case that if you enable mouse events, curses turns off
> automatic translation of scroll wheel to scrolling?

I was not aware of that, and have never seen this behavior.
How does that work, how is the mouse wheel currently translated to
window scrolling?


Hannes

  reply	other threads:[~2021-03-11 17:48 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210306173417.21528-1-ssbssa.ref@yahoo.de>
2021-03-06 17:33 ` [RFC] TUI windows for locals/display/threads/frames/memory Hannes Domani
2021-03-06 17:33   ` [PATCH 01/22] Initial TUI mouse support Hannes Domani
2021-03-11 17:32     ` Tom Tromey
2021-03-11 17:48       ` Hannes Domani [this message]
2021-03-12 16:35         ` Tom Tromey
2021-03-12 16:43           ` Hannes Domani
2021-03-12 17:02             ` Tom Tromey
2021-03-06 17:33   ` [PATCH 02/22] Create/disable/enable/delete breakpoints in TUI with mouse Hannes Domani
2021-03-08  9:32     ` Andrew Burgess
2021-03-08 12:00       ` Hannes Domani
2021-03-11 21:17         ` Tom Tromey
2021-03-11 21:16     ` Tom Tromey
2021-03-06 17:33   ` [PATCH 03/22] Forward mouse click to python TUI window Hannes Domani
2021-03-06 18:09     ` Eli Zaretskii
2021-03-08  9:36     ` Andrew Burgess
2021-03-11 21:19       ` Tom Tromey
2021-03-11 21:20     ` Tom Tromey
2021-03-06 17:33   ` [PATCH 04/22] Prevent flickering when redrawing the TUI python window Hannes Domani
2021-03-11 21:21     ` Tom Tromey
2021-03-06 17:34   ` [PATCH 05/22] Implement locals TUI window Hannes Domani
2021-03-08  9:51     ` Andrew Burgess
2021-03-11 21:26       ` Tom Tromey
2021-03-11 21:33     ` Tom Tromey
2021-03-11 22:00     ` Tom Tromey
2021-03-06 17:34   ` [PATCH 06/22] Implement display " Hannes Domani
2021-03-11 21:37     ` Tom Tromey
2021-03-06 17:34   ` [PATCH 07/22] Implement threads " Hannes Domani
2021-03-06 17:34   ` [PATCH 08/22] Implement frames " Hannes Domani
2021-03-11 21:40     ` Tom Tromey
2021-03-11 21:50       ` Hannes Domani
2021-03-06 17:34   ` [PATCH 09/22] Implement cccw TUI command Hannes Domani
2021-03-08 10:24     ` Christian Biesinger
2021-03-11 21:42       ` Tom Tromey
2021-03-11 21:57   ` [RFC] TUI windows for locals/display/threads/frames/memory Tom Tromey

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=610501495.582273.1615484929627@mail.yahoo.com \
    --to=ssbssa@yahoo.de \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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).