Well, ideally we would develop a full-blown DRC library to run
through all the nodes. BUT, if we just want to check overlaps, it would
be a bit easier. We already store a bounding box dimension for every
element, so it would be pretty straightforward to do a rough check to
see which overlap. For detailed checks (for macros and complex items),
we could always use cairo to render the two elements in question, with
the second element drawn in a transparent color. Then we would check
the pixmap for any pixels with the combined color.
We also already have a "selection group" (really, a GArray of
gerbv_selection_item_t items), so the function could just pass back a
selection group with all the elements together.
e.g.:
GArray *
gerbv_return_continuous_path ( &project, inputXcoord , inputYcoord );
The return array can easily be passed to the main renderer to display it
as a selected group.
Alternatively, we could focus on getting a PCB file export working well,
and then do it through PCB maybe?
Cheers,
Julian
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Gerbv-devel mailing list
Gerbv-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gerbv-devel
