Hi Emily,
There's a disconnect with the NavigatePanel and the PanFactor it is
supposed to use - the panel never actually uses the pan factor. It's
a rather old disconnect, unfortunately.
The problem is that the PanFactor is defined as percentage of screen
to move. The calls that it makes need the pan value to be in decimal
degrees. We've never written a generic translator for all projection
types to cross the line for those different definitions. The reason
it works now is that the projections have a default method for
handling pans when no distance is given.
Actually, I've just thought of a solution to this, after all these
years - the NavigatePanel needs to be a ProjectionListener and
maintain a copy of the projection to use for these calculations, so it
can do that translation based on the map size and some inverse
projection calculations. I'll try to get this in the next release.
Sorry about this,
Don
On Feb 2, 2009, at 2:41 PM, Emily.Juricek_at_l-3com.com wrote:
> Thanks in advance for the help. I sent this post but we changed our
> email and I cannot find the answer on the archives so any help would
> be appreciated.
>
> I need to change the Pan of the map to pan 50% instead of the
> default which seems to be 25%. I have tried to set the Pan value but
> it is not working. When I looked into the source code, it appears
> that no matter what the value I set the pan size to be, the size is
> being divided by 2. I am using version 4.6.4 of OpenMap.
>
>
> Thanks.
>
> Emily
>
--
[To unsubscribe to this list send an email to "majdart_at_bbn.com"
with the following text in the BODY of the message "unsubscribe openmap-users"]
Received on Thu Feb 05 2009 - 17:54:44 EST