kicad-developers team mailing list archive

["jean-pierre.charras@..." <jean-pierre.charras@...>]

Obviously, tests must be done before any conclusion.
remember also wxWidget 3.0 could have some important changes in graphic 
functions
Tests must be always done using macOSX, Linux and Windows (Windows 7 has 
more problems).

Currently wxDC (using the last fast algo to draw grid) works (although 
some artifacts when scrolling the window) under Linux XP, and Windows 7.
(seems works Ok also under OSX)

I suggest to guys who want test wxGCDC, or wxGraphicsContext to use the 
wxWidget sample "drawings"
A lot of tests can done with adding only very few code (Grid, texts, 
arc, circles, polygons and lines can be easily tested).
Just modify this sample to draw 30000 to 60000 items and many more:
many copper zones use up to 20000 and more segments outlines per solid 
polygon (and there are more than one copper zone in a design).
a grid can uses 500x300 pixels so 150000 pixels must be drawn (and needs 
only few lines of code).
So guides are:
Draw a *lot of* items, mainly thick lines and polygons.
Use small and also very large values for coordinates (bigger than 2**16) 
to find problems like overflows.

So no need to create branches in kicad just to see if a graphic library 
is working (and how it works).
Just one file (drawing.cpp) is enough
(I used many times this sample to test (and to find...) graphic problems 
using wxDC)

One can also have a look to sfml (open source and gpl: see 
http://www.sfml-dev.org/ ) to test it
(the author claims it is very fast, multi platform and wxWidgets 
compatible).

But we need tests and volunteers to code these tests.
No decision can be made without serious tests.

--
Jean-Pierre CHARRAS

Maître de conférences
Directeur d'études 2ieme année.
Génie Electrique et Informatique Industrielle 2
Institut Universitaire de Technologie 1 de Grenoble
BP 67, 38402 St Martin d'Heres Cedex

Recherche :
GIPSA-LAB - INPG
Rue de la Houille Blanche
38400 Saint Martin d'Heres