I have drafted a blueprint, on how we could implement a QA system from the
python-side.
https://blueprints.launchpad.net/kicad/+spec/python-pcbnew-qa-tests
The specifications are free to edit or comment.
If you have a moment, please give it a read, and comment on this thread.
Also ideas on
I have drafted a blueprint, on how we could implement a pluggable IO
modules.
*https://blueprints.launchpad.net/kicad/+spec/pluggable-file-io*
If you have a moment, please give it a read, and comment on this thread or
edit over the draft if you feel something is plain wrong.
Dick, I really
On 09/16/2013 09:21 AM, Miguel Angel wrote:
I have drafted a blueprint, on how we could implement a pluggable IO
modules.
_https://blueprints.launchpad.net/kicad/+spec/pluggable-file-io_
If you have a moment, please give it a read, and comment on this thread
or edit over the draft if you feel
Hi Tomasz, thanks a lot for reading comments.
2013/9/16 Tomasz Wlostowski tomasz.wlostow...@cern.ch
On 09/16/2013 09:21 AM, Miguel Angel wrote:
_https://blueprints.launchpad.**net/kicad/+spec/pluggable-**file-io_https://blueprints.launchpad.net/kicad/+spec/pluggable-file-io_
Hi Miguel,
The reason I'm worried regarding these backups is because of the
possibility that you can get hit by a train. In that case nobody
would have access to the backups, I'm afraid. That's why I proposed
automatically uploading the non privacy sensitive tables to a public
repo on a regular basis.
On
Laszlo, please, don't offtopic the thread, going offtopic on development
threads only slow things down...
I already replied you on the kicad user list. I don't have the time to
setup what you wanted, the architecture I have is enough.
I can provide password access to the backups machine to
More detail about this, it happens to me with bzr4313 and bzr4107 , I don't
remember having problems with
this previously.
When I move a block of components, the grid snap works.
If I move a single component ('M key') it moves, with no snap.
If I draw a wire, no snap.
Could it be a
I highly suspect that this behaviour comes from here
(eeschema/controle.cpp), may be a wxBug(tm) related to Mac OSX? ..
this look like a lot of conditions to get satisfied by a bug..:
if( !aHotKey wxGetKeyState( WXK_SHIFT ) wxGetKeyState(
WXK_CONTROL ) )
snapToGrid = false;
It really seems like a wx/MACOSX related bug to me,
printf(snapToGrid: %d , aHotkey:%d WXKSHIFT: %d, WXKCONTROL:
%d\n,snapToGrid,aHotKey ,wxGetKeyState( WXK_SHIFT ), wxGetKeyState(
WXK_CONTROL ));
always print WXK_SHIFT and WXK_CONTROL as true
snapToGrid: 0 , aHotkey:0 WXKSHIFT: 1,
On 09/16/2013 03:54 PM, Miguel Angel wrote:
It really seems like a wx/MACOSX related bug to me,
Miguel,
Welcome to the wonderful world of cross-platform compatibility of
wxWidgets. This is exactly why we (me Orson) don't want to use any
sort of wx events in new tools.
Cheers,
Tom
Arf, I already had my own personal welcome, when I started using kicad on
OSX,
packed Marco Serantoni wx patches into the KiCad builder.. and then Felix
Morgner contributed
a few more.
It looks like we will have a new one soon.
wxwidgets for macosx seems to poll over all the system available
On 09/16/2013 09:01 AM, Tomasz Wlostowski wrote:
On 09/16/2013 03:54 PM, Miguel Angel wrote:
It really seems like a wx/MACOSX related bug to me,
Miguel,
Welcome to the wonderful world of cross-platform compatibility of
wxWidgets. This is exactly why we (me Orson) don't want to use any
12 matches
Mail list logo