Mail Archives: geda-user/2012/07/12/08:00:50
> Very nice, but shouldn't you pick the center of the component instead
> of its lower left, or why not picking the lower left of the refdes,
> which is the thing one is loocking for when searching, that should be
> easy to find for the program ?
That is a good point. I'm impressed you figured that out. Did you get
the script running or did you read though script? If you get an itch for
it, send me a patch which corrects it. If the script is not parsing the
component width, it shouldn't be that hard to add it to the model.
> Instead of forcing the user to tell the program the bonding box, why
> not scan through it (recursively), let the program do the job?
I thought about that and while finding the width and height of the page
is somewhat straightforward, scanning and obtaining the number of visual
rows and columns the sheet is divided into could be interesting. (What
is the "largest" single letter, and single number text field ..)
Especially as you would also be guessing as to which symbol even is the
title page. (who's the biggest, who has the term title in the
filename...) It would take less work and be more reliable, to go ahead
and create all the entries for all the different title pages. If
someone were to create their own brand new sheet the guess algorithms
for identifying and profiling the sheet might not work anyway.
> What is the interface to finding symbols, is it in libgeda or in scheme?
The python script parses the ASCII schematic files themselves. (woot
human readable format)
- Raw text -