- **Milestone**: --> OJ_future
---
** [bugs:#476] Optimize rendering process**
**Status:** open
**Milestone:** OJ_future
**Created:** Sun May 13, 2018 06:23 PM UTC by michael michaud
**Last Updated:** Sun May 13, 2018 10:10 PM UTC
**Owner:** michael michaud
After a pan or a zoom, the view is redrawn.
I catched and displayed the calls tofeature# getGeometry() method in the
console and get not less than 5 calls coming from
renderer.ThreadQueue$Worker#run() for one object after a pan.
With a large dataset, one can see that if it takes x seconds to redraw the
screen, the clock indicating the running process lasts about 2x (not 5x).
I think that some rendering processes are started but interrupted by a new one,
and one of them starts at the end of the first one, doubling the total
rendering duration.
Context : I try to write a database driver which does not load features but
call getGeometry()/ getAttribute() every time it needs to. Not sure it will be
usable, especially if OpenJUMP call geometries and attributes more thanwhat is
strictly necessary.
---
Sent from sourceforge.net because jump-pilot-devel@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/jump-pilot/bugs/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/jump-pilot/admin/bugs/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
