kicad-developers team mailing list archive
Mailing list archive
Re: Decoupling issues with python
It could make sense to have that attribute (filename) in BOARD itself, but
we should check with the others.
Then think how SCREEN or FRAME an get access to the name yet, I suppose
straight forward if SCREEN/FRAME is shared among the different tools,
but may be BOARD and "schematic file" have a common ancestor that can hold
the method to get the filename?
2012/8/13 Lorenzo Marcantonio <l.marcantonio@xxxxxxxxxxxx>
> On Mon, Aug 13, 2012 at 08:51:04AM +0200, Miguel Angel wrote:
> > For acessing the current board in scripting you can use 'GetBoard' it's
> a scripting helper which receives our pcb_edit_frame as pcbnew.cpp boots up.
> I know that... the problem is accessing the SCREEN or the FRAME from the
> board! The real issue is that some data are mislocated (probably from
> the original structure of kicad when it was converted to C++...) and the
> fact that that issue is shared by eeschema too (via inheritance)
> More simply, the 'big' issue at the moment is:
> - I have a BOARD*; how can I get the board filename from that? AFAIK it
> isn't possible...
> Lorenzo Marcantonio
> Logos Srl
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
Miguel Angel Ajo Pelayo
+34 636 52 25 69