> > A problem that we have is when you zoom in or out to extreme distances
> > Graphics2D eventually chokes and wont draw anything. And this is
> > understandable since the numbers are running out of resolution at these
> > large scaling.
>
> What is probably happening is that our rendering code is choking on
> math overflows in the integer device space when the coordinates get
> too much larger than a short (short * short == int, anything larger
> and the int overflows on multiplies). Are you using regular or
> antialiased rendering? Have you tried both?
>
> Can you send me a small standalone test case?
>
> ...jim
A followup question on the same topic: I am seeing problems in my application that
maps projective geometry surfaces to each other (so the coordinates can get
arbitrarily big near singular points). The above post implies that perhaps we should
avoid coords > 2**16 ?
In my case, things are ok with graphics2D.fill(generalPath) even when coords are in
the range 1.0E10. But then simple things like drawing a line with
graphics2D.draw(generalPath) with coords
(1.5671567103433672E10 -4.1991837501276317E9) to (3.768179037202709E-13
2.8914254707822145E-13
) hangs the JVM.
This does not seem to depend on how zoomed in or out I am. Its a bit confusing as to
when bad things will happen and why. Any hints into the inner mysteries would be
appreciated :^}
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA2D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
