More eye-candy.. again, a real screen-shot, not a mockup. http://www2.eng.cam.ac.uk/~pcjc2/geda/drc_for_real2.png
Still not production ready though.. whenever I play with GL, I seem to have a knack of making enough errors in my code to find unusual X / 2D driver / Mesa bugs which crash the X server!). The current implementation crashes (the X server) occasionally, and is somewhat slow at repainting the DRC window. I can fix the slowness (and probably the crash) by pre-computing the little pixmaps showing the violations rather than drawing them each repaint, but then they are drawn in ugly colours due to the in-progress DRC check. The implementation I have now shows them as on the board, in real-time. I say "fix the crash"... calling the GL routines to render once per violation is a lot less exposure to race conditions / other badness than calling them for every visible violation, for every repaint. Regards, -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) _______________________________________________ geda-user mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
