Hi, I recently discovered that a recent commit introduce a significant change on CPU usage. The commit is 71eff775d86be02173e28421cea7f7d3f5a8344. It offers a smooth pan when drag&drop, but it introduces a huge amount of tile requests.
For exemple, when I drag the map, I quickly observe around 600 requests on local tile cache while around 10 requests would be enough. The matter is, in order to keep a smooth dragging, the viewport is requested to redraw completly. While doing this, all displayed maps need to check their local cache. And this, for each X event. I found a quick hack for this, but I'm not really proud of it: I do not take time to understand current logic of all this, specially the logic changed by the guilty commit. The idea is to use VikViewport to store a new boolean to inhibit autodownload feature while a drag is in action. Can someone review my patch and give me some tips to do a better job? Thanks in advance. -- Guilhem BONNEFILLE -=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com -=- mailto:guilhem.bonnefi...@gmail.com -=- http://nathguil.free.fr/
autodownload.patch
Description: Binary data
------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
