You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: tcarter[at]noggin.com.au [Submitted to the original trac issue database at 10.12am, Saturday, 30th August 2008]
The native render function incorrectly determines that things are not in the viewport at high lat or long values (eg 151), this seems to be due to an integer overflow in CoordBox::center() which uses (BottomLeft + TopRight)/2 to calculate the center of the CoordBox
The attached patch resolves this, at least in my testing.
The text was updated successfully, but these errors were encountered:
Author: koying [Added to the original trac issue at 3.48pm, Tuesday, 2nd September 2008]
(In [10406]) ADD : revised OSB format. Allows to use large map files directly from disk with low memory footprint.
FIX : Native render doesn't render anything at high lat/long values (Closes #1135)
FIX : Expand tables in the properties dock to the available width by default (Closes #1136)
Reporter: tcarter[at]noggin.com.au
[Submitted to the original trac issue database at 10.12am, Saturday, 30th August 2008]
The native render function incorrectly determines that things are not in the viewport at high lat or long values (eg 151), this seems to be due to an integer overflow in CoordBox::center() which uses (BottomLeft + TopRight)/2 to calculate the center of the CoordBox
The attached patch resolves this, at least in my testing.
The text was updated successfully, but these errors were encountered: