From: Gerd Hoffmann <kraxel@redhat.com>
To: Dongwon Kim <dongwon.kim@intel.com>
Cc: Khairul Anuar Romli <khairul.anuar.romli@intel.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH 1/4] ui/gtk-egl: un-tab and re-tab should destroy egl surface and context
Date: Tue, 2 Nov 2021 14:37:50 +0100 [thread overview]
Message-ID: <20211102133750.2s5elsswxtkfbn5y@sirius.home.kraxel.org> (raw)
In-Reply-To: <20210917001320.6515-2-dongwon.kim@intel.com>
On Thu, Sep 16, 2021 at 05:13:17PM -0700, Dongwon Kim wrote:
> An old esurface should be destroyed and set to be NULL when doing
> un-tab and re-tab so that a new esurface an context can be created
> for the window widget that those will be bound to.
Fails to build on windows (probably also on --disable-opengl builds).
take care,
Gerd
next prev parent reply other threads:[~2021-11-02 13:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 0:13 [PATCH 0/4] ui/gtk-egl: fix for untab/tab problem Dongwon Kim
2021-09-17 0:13 ` [PATCH 1/4] ui/gtk-egl: un-tab and re-tab should destroy egl surface and context Dongwon Kim
2021-11-02 13:37 ` Gerd Hoffmann [this message]
2021-11-02 22:36 ` [PATCH v2 " Dongwon Kim
2021-11-02 22:36 ` [PATCH 2/4] ui/gtk-egl: make sure the right context is set as the current Dongwon Kim
2021-11-02 22:36 ` [PATCH 3/4] ui/gtk-egl: guest fb texture needs to be regenerated when reinitializing egl Dongwon Kim
2021-11-02 22:36 ` [PATCH 4/4] ui/gtk: gd_draw_event returns FALSE when no cairo surface is bound Dongwon Kim
2021-09-17 0:13 ` [PATCH 2/4] ui/gtk-egl: make sure the right context is set as the current Dongwon Kim
2021-09-17 0:13 ` [PATCH 3/4] ui/gtk: gd_draw_event returns FALSE when no cairo surface is bound Dongwon Kim
2021-09-17 0:13 ` [PATCH 4/4] ui/gtk-egl: guest fb texture needs to be regenerated when reinitializing egl Dongwon Kim
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=20211102133750.2s5elsswxtkfbn5y@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=dongwon.kim@intel.com \
--cc=khairul.anuar.romli@intel.com \
--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).