Hi Andreas and Nicolas,
In the bug report, I mentioned that using trucation
(as opposed to floor ) had problems and pointed out
that with the present implementation (where trucation
is done separately for origin and corner) you could
not count on
aRectangle truncated extent = aRectangle extent
truncated
to always be true. I meant that as a dramatization of
the problem not its sole difficulty.
Andreas method could make that true but the truncation
of the origin would still cause the bounds to jitter
as quadrents are crossed. So it would not represent a
complete solution to the truncation and rounding
problem.
Yours in service, --Jerome Peace
>Truncation and round off
>Andreas Raab andreas.raab at gmx.de
>Sun Feb 5 21:22:25 CET 2006 wrote:
>
>
>nicolas cellier wrote:
>> Putting a constraint like:
>> aRectangle truncated extent = aRectangle extent
truncated
>> whatever the coordinate transform is does not sound
easy: maths say it is
>> simply impossible even without a rotation (unless
rectangle sides are 3*n and
>> 4*n).
>
>Huh? And why would that be? The correct solution for
that sort of
>truncation is obviously:
>
>Rectangle>>truncated
> ^Rectangle origin: self origin truncated extent:
self extent truncated
>
>I see nothing that suggests there would be any
difficulty.
Well, at the speed at which you program I would
imagine most fenceposts appear as blurs anyway. ;-p
>
>Cheers,
> - Andreas
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Locked
