Hi Ruben,
All of the suggestions posted are excellent, but Jesper points a key
question. I know you say that 40ms repaint is a requirement, but why?
Are you tracking things that are moving? How many? Updating at that
rate will involve a lot of rendering for very little payoff - zoomed
out maps will have objects barely moving at that frame rate unless
they are moving very fast, but even then it would be hard to see
changes at that rate. You might want to check to see if the map
location of your objects have changed before deciding to repaint,
instead of checking whether the objects have moved geospatially. If
you are changing how things look (vibrating map objects to highlight
them, changing their color, etc), I can understand why you would want
the update rate to be something higher. In that case, you might want
to buffer several maps together with different rendering parameters,
and then loop that set.
- Don
On Mon, May 23, 2011 at 7:25 AM, Jesper Berglund
<jesper.berglund_at_pertexo.se> wrote:
> Has the map changed during the 40ms, like panning or zooming?
> Is there objects on the map which has changed?
>
> Don't repaint all layers, only those who might have changed.
>
> Repaint only on changes of data.
>
> If there is a burst of events, coalesce during a timeperiod and then repaint
> using javax.swing.Timer .
>
> These are the measures that I have made in my Openmap app.
>
> HTH
>
> /Jesper
>
> Ruben DF skrev 2011-05-23 11:30:
>>
>> Hi,
>>
>> I'm afraid I cannot repaint each 500 ms or longer...it's a customer's
>> requirement... :(
>>
>> Thanks anyway!
>
> --
> [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"]
>
--
[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 Mon May 23 2011 - 12:19:17 EDT