From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92309] Box drawn around cursor in multiple 3D games
Date: Wed, 02 Dec 2015 15:42:11 +0000 [thread overview]
Message-ID: <bug-92309-502-wzpr7vypF7@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92309-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 913 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92309
--- Comment #17 from acutiator@outlook.com ---
> How would the xserver know what the game intends in the cursor image?
This is what I'm asking you, actually. I don't know if it's possible. I'm
asking if it is. From what I understand based on the comments by Michel and
Kamil it sounds like it should be possible. So I wanted to clarify on whether
or not it is. The comment about a (0,0,0,0) pixel being a clear indicator that
something is wrong is what triggered my question. If it can be clearly detected
that it's a premultiplied alpha, even when the program doesn't indicate this, I
would think that should be implemented. Now the question is if that can be
easily detected without human intervention. But based on your question to me it
doesn't sound like it is. Is that correct?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1684 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-12-02 15:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 2:16 [Bug 92309] Box drawn around cursor in multiple 3D games bugzilla-daemon
2015-10-06 2:16 ` bugzilla-daemon
2015-10-06 2:17 ` bugzilla-daemon
2015-10-06 2:21 ` bugzilla-daemon
2015-10-06 2:48 ` bugzilla-daemon
2015-10-06 2:49 ` bugzilla-daemon
2015-10-06 2:56 ` bugzilla-daemon
2015-10-21 6:04 ` bugzilla-daemon
2015-10-25 10:19 ` bugzilla-daemon
2015-10-25 10:20 ` bugzilla-daemon
2015-10-25 10:21 ` bugzilla-daemon
2015-10-27 6:23 ` bugzilla-daemon
2015-10-27 8:37 ` bugzilla-daemon
2015-12-01 15:10 ` bugzilla-daemon
2015-12-01 15:36 ` bugzilla-daemon
2015-12-02 2:45 ` bugzilla-daemon
2015-12-02 4:48 ` bugzilla-daemon
2015-12-02 15:27 ` bugzilla-daemon
2015-12-02 15:42 ` bugzilla-daemon [this message]
2015-12-02 16:17 ` bugzilla-daemon
2015-12-02 17:16 ` bugzilla-daemon
2016-07-15 14:03 ` bugzilla-daemon
2016-07-15 14:09 ` bugzilla-daemon
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=bug-92309-502-wzpr7vypF7@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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