[cairo] Why PIXMAN_MAX_INT is defined as "((pixman_fixed_1 >> 1) - pixman_fixed_e)" ?
seongwon1.cho at samsung.com
Fri Apr 12 00:09:28 PDT 2013
Thank you for your advise.
I have suggested to fix this problem in App side.
------- Original Message -------
Sender : Siarhei Siamashka<siarhei.siamashka at gmail.com>
Date : 2013-04-11 08:55 (GMT+09:00)
Title : Re: [cairo] Why PIXMAN_MAX_INT is defined as "((pixman_fixed_1 >> 1) - pixman_fixed_e)" ?
On Wed, 10 Apr 2013 05:19:06 +0000 (GMT)
> Hi, all
> I have a simple question.
> Why PIXMAN_MAX_INT is defined as "((pixman_fixed_1 >> 1) - pixman_fixed_e)" ?
Pixman code was originally a part of Xorg server, which only needs and
uses 16.16 fixed point format:
> Is there anyway to overcome this limitation?
Some of the 16-bit limitations are already removed. Some of them are
still there. Fixing all of the remaining 16-bit assumptions in one go
(and actually confirming that the problems are indeed fixed) may
require a non-trivial amount of work.
But what exactly are you trying to do and how do you hit this
PIXMAN_MAX_INT limitation? A "realistic" approach is to try fixing
problems as they are discovered and extend the pixman test suite
to make sure that these problems don't show up again.
I may be wrong, but pixman users seem to generally prefer workarounding
these problems (for example, by splitting rendering into smaller
chunks) instead of reporting bugs and/or complaining. So the issue
is not getting enough attention.
조 성 원 선임/ SeongWon Cho
SLP R&D Group
Mobile Device Division.
Samsung Electronics Co. Ltd.
Phone : +82-31-301-5373 Mobile : +82-10-7260-5373
Mail : seongwon1.cho at samsung.com
More information about the cairo