From: Anthony Liguori <anthony@codemonkey.ws>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 1/3] cursor: add cursor functions.
Date: Wed, 19 May 2010 14:08:28 -0500 [thread overview]
Message-ID: <4BF4372C.7060000@codemonkey.ws> (raw)
In-Reply-To: <AANLkTilmb4tTUtzhQE6utAMMDdoYDl0cIQlr3FfuJw4C@mail.gmail.com>
On 05/19/2010 01:57 PM, Blue Swirl wrote:
> On 5/19/10, Gerd Hoffmann<kraxel@redhat.com> wrote:
>
>>>
>>>>
>>>>> Then there would be no need of parsing.
>>>>>
>>>>>
>>>> You would need _two_ bitmaps (e.g. mask and cursor, so that mask=1
>>>>
>> gives
>>
>>>> transparent, mask=0 cursor=0 gives black and mask=0 cursor=1 gives
>>>>
>> white).
>>
>>>>
>>> Yes, but it's still packed more efficiently.
>>>
>>>
>> Well. You can't have both. We can have a efficiently packed format (i.e.
>> two bitmaps). Or we can do it in a way which doesn't need parsing, but that
>> wouldn't be the most compact format ...
>>
> You're right, so packing or introducing a small conversion function is
> not critical. I'd still prefer a standard format if possible.
>
Personally, I'd rather see Gerd's original format but read from a file
instead of hard coded in a .c file. IOW, a
/usr/share/qemu/default-cursor.qpm that contained the appropriate
strings. A couple extra lines that made it an xpm I think would be
worth it too.
Regards,
Anthony Liguori
>>> There's yet another way:
>>> #define _ 0,
>>> #define X 0xff000000,
>>> #define o 0xffffffff,
>>> {
>>> _ _ _ X o X _ _ _
>>> }
>>> #undef _
>>> #undef X
>>> #undef o
>>>
>>>
>> Neat idea ;)
>>
>> cheers,
>> Gerd
>>
>>
>>
>
next prev parent reply other threads:[~2010-05-19 19:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 12:51 [Qemu-devel] [PATCH 0/3] local cursor patches Gerd Hoffmann
2010-05-05 12:51 ` [Qemu-devel] [PATCH 1/3] cursor: add cursor functions Gerd Hoffmann
2010-05-06 18:12 ` Blue Swirl
2010-05-06 19:27 ` Gerd Hoffmann
2010-05-06 19:42 ` Blue Swirl
2010-05-07 7:05 ` [Qemu-devel] " Paolo Bonzini
2010-05-07 15:23 ` Blue Swirl
2010-05-19 8:16 ` Gerd Hoffmann
2010-05-19 18:57 ` Blue Swirl
2010-05-19 19:08 ` Anthony Liguori [this message]
2010-05-20 12:49 ` Gerd Hoffmann
2010-05-20 13:17 ` Anthony Liguori
2010-05-05 12:51 ` [Qemu-devel] [PATCH 2/3] use new cursor struct + functions for vmware vga and sdl Gerd Hoffmann
2010-05-05 12:51 ` [Qemu-devel] [PATCH 3/3] vnc: rich cursor support Gerd Hoffmann
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=4BF4372C.7060000@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.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).