kicad-developers team mailing list archive

[Brian Sidebotham <brian.sidebotham@xxxxxxxxx>]

On 24 October 2012 23:23, Brian Sidebotham <brian.sidebotham@xxxxxxxxx> wrote:
> On 24 October 2012 21:20, Miguel Angel Ajo Pelayo <miguelangel@xxxxxxx> wrote:
>>
>> Wow wow woow!!! :D
>>
>> If you're using console Python, and call import pcbnew, then you should use
>> LoadBoard("xxxxx"),
>>
>> http://bazaar.launchpad.net/~kicad-testing-committers/kicad/testing/view/head:/pcbnew/scripting/examples/listPcb.py
>>
>> if it's a pcbnew console inside pcbnew window, then It really seems like the
>> pcbnew is reloading the
>> pcbnew.dll and then GetBoard cannot find the "frame" pcb, in that case try
>> to put the .dll out of path
>> for the pcbnew .exe
>
> Thanks for the info Miguel.
>
> I can't find any trace of scripting within PCBNEW in this build. Is
> there something that would hint to me that it is actually a scripting
> build?
>
> I don't see anything that will let me have a scripting window inside
> the PCBNEW frame. I've tried moving the python.py _python.pyd and
> libpcbnew.dll.a files outside of the bin directory, but with no
> change. I have been simply running python from the console, but it
> sounds like that's not right if I want to interact with PCBNEW
> directly.
>
> The console mode appears to work fine for working on files and stuff
> using the LoadBoard().
>
> Thanks for your continued work on scripting! :-)
>
> Best Regards, Brian.

Ah, sorry for the lack of accurate information - I should add that I
didn't enable the wxpython option as I wanted to keep things simple to
begin with. Perhaps this is a pre-requisite of having a console window
in PCBNEW?

Best Regards, Brian.