>> * Skip making it an option. The benefits are good enough to have it >> permanently on. And I doubt that 99% of the users know what it does, how >> it works and why to use this option anyway. > > ok, we just have to find a good value for ε then. I'll keep it in > QSettings for the time being and just remove it from the UI, ok?
Hm, ok. In a year we will wonder what this peculiar value is good for :) > >> * But switch it off for closer zoom levels. Map contributor will get a >> heart attack if they do not see their polyline as defined. On closer >> views the speed up is not noticeable anyway. > > ok, although in principle this should not be necessary, as ε is > expressed in pixel units anyway. Where do the closer zoom levels begin? I would say at zoomFactor <= 2.0 because at this zoom factor the map resolution gets 24 bit which is the highest one. > >> * Get rid of that class in a method. :) That is ugly. And it only >> defines a single method anyway. > > Well, it defines a local function, something that isn't allowed in C++. > I don't think it's *that* ugly, but I'll remove it ;-) A good old trusty private method is well enough :) Oliver ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
