qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Joshua Watt <jpewhacker@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	jtomko@redhat.com, libvir-list@redhat.com,
	Markus Armbruster <armbru@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v3 5/7] ui/gtk: implement show-cursor option
Date: Fri, 7 Feb 2020 08:37:13 -0600	[thread overview]
Message-ID: <b0dca00d-5d35-a139-b5d0-1777c92b23a0@gmail.com> (raw)
In-Reply-To: <20200207101753.25812-6-kraxel@redhat.com>


On 2/7/20 4:17 AM, Gerd Hoffmann wrote:
> When specified just set null_cursor to NULL so we get the default
> pointer instead of a blank pointer.
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
>   ui/gtk.c | 8 ++++++--
>   1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/ui/gtk.c b/ui/gtk.c
> index d18892d1de61..a685d1ae0848 100644
> --- a/ui/gtk.c
> +++ b/ui/gtk.c
> @@ -2243,8 +2243,12 @@ static void gtk_display_init(DisplayState *ds, DisplayOptions *opts)
>       textdomain("qemu");
>   
>       window_display = gtk_widget_get_display(s->window);
> -    s->null_cursor = gdk_cursor_new_for_display(window_display,
> -                                                GDK_BLANK_CURSOR);
> +    if (s->opts->has_show_cursor && s->opts->show_cursor) {
> +        s->null_cursor = NULL; /* default pointer */
> +    } else {
> +        s->null_cursor = gdk_cursor_new_for_display(window_display,
> +                                                    GDK_BLANK_CURSOR);
> +    }

I think it would make more sense to have all the logic related to what 
cursor is used in the same location, instead of split up between here 
and gd_update_cursor(). This would also match the behavior of the SDL 
and cocoa backends a little better.

>   
>       s->mouse_mode_notifier.notify = gd_mouse_mode_change;
>       qemu_add_mouse_mode_change_notifier(&s->mouse_mode_notifier);


  reply	other threads:[~2020-02-07 15:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-07 10:17 [PATCH v3 0/7] ui: rework -show-cursor option Gerd Hoffmann
2020-02-07 10:17 ` [PATCH v3 1/7] ui: add show-cursor option Gerd Hoffmann
2020-02-07 13:56   ` Markus Armbruster
2020-02-07 10:17 ` [PATCH v3 2/7] ui: wire up legacy -show-cursor option Gerd Hoffmann
2020-02-07 10:17 ` [PATCH v3 3/7] ui/sdl: switch to new show-cursor option Gerd Hoffmann
2020-02-07 10:17 ` [PATCH v3 4/7] ui/cocoa: " Gerd Hoffmann
2020-02-07 10:17 ` [PATCH v3 5/7] ui/gtk: implement " Gerd Hoffmann
2020-02-07 14:37   ` Joshua Watt [this message]
2020-02-12 11:57     ` Gerd Hoffmann
2020-02-07 10:17 ` [PATCH v3 6/7] ui: drop curor_hide global variable Gerd Hoffmann
2020-02-07 10:17 ` [PATCH v3 7/7] ui: deprecate legacy -show-cursor option Gerd Hoffmann
2020-02-08 22:52 ` [PATCH v3 0/7] ui: rework " Ján Tomko

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=b0dca00d-5d35-a139-b5d0-1777c92b23a0@gmail.com \
    --to=jpewhacker@gmail.com \
    --cc=armbru@redhat.com \
    --cc=jtomko@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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 NNTP newsgroup(s).