Peter Clifton wrote: > The "polygon_speedup" branch should mostly be a success, but I'm fairly > sure it does increase CPU cycles for some operations. I've not had a > chance to test it very scientifically, and I'm hesitant to push it to > git HEAD without having at least made a few checks to see that it isn't > penalising too many general cases.
Is there anything us testers can check or test? > If necessary I could re-write the polygon rendering routines to NOT rely > on the fact the "polygon_speedup" branch creates a spatial datastructure > of all the contours within a polygon. If it is just about polygons, I'd say "Go ahead and push!". On my fairly recent desktops(*) your openGL branch is consistently faster than HEAD. On machines with less CPU and graphics muscles I would disable polygons during manual routing, anyway. So slightly increasing the CPU load for polygons won't affect the work-flow in an environment with weak hardware too much. On the other hand, the huge usability improvement due to transparent tracks helps in such an environment, too. By the way: Do you you intend to keep the very nice see-thru feature in thin-draw-poly mode? If so, there should be an additional menu item to explicitly disable any polygon calculation. I used to work-around the lack of such a menu item by moving the polygons to dedicated layers and put the layers in special layer groups. This is really a crutch which should not be necessary. ---<)kaimartin(>--- (*) one of them is three and a half years old, now. The other received an update to double core AMD a few weeks ago. -- Kai-Martin Knaak tel: +49-511-762-2895 Universität Hannover, Inst. für Quantenoptik fax: +49-511-762-2211 Welfengarten 1, 30167 Hannover http://www.iqo.uni-hannover.de GPG key: http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmk&op=get _______________________________________________ geda-user mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
