During today merge I spotted this thing in backanno.cpp:
/* Give a reasonable value to the field position and
* orientation, if the text is empty at position 0, because
* it is probably not yet initialized
*/
if( fpfield->m_Text.IsEmpty() &&
( fpfield->GetPo
> Hi Cirilo,
I'm sorry that I forgot to add:
When I last made an HPGL plot using the Fedora 16 version of Kicad, I
noticed that the HPGL files were simple outlines only. A long
trace was a combination of rectangles with circles drawn at every
joint and at the ends.
The plot files did not ut
Hi Cirilo,
> When I did that sort of thing 15 years ago the pen I used was the type
> used for stencil work - it was a short steel tube (you can get
> various sizes) with a steel plug. I can't remember what ink I used
> now - it was a pretty thick in k meant for old drum recorders but it
> was a
- Original Message -
> From: Øyvind Aabling
> To: Andreas Beutling
> Cc: KiCad Developers
> Sent: Tuesday, February 5, 2013 2:20 AM
> Subject: Re: [Kicad-developers] HPGL
>
[snip]
>
> Hi Andreas.
>
> Have I understood this correctly: You're using
> a pen plotter to print directly on
Hello Øyvind,
Have I understood this correctly: You're using
a pen plotter to print directly on the PCB ?
Yes.
Is this the etch pattern or the silkscreen,
and which type(s) of pen(s) are you using ?
The plotter draw directly the etch pattern on the PCB.
The pens are home made: Old HP pen w
On Sun, 3 Feb 2013, Andreas Beutling wrote:
Hello Dick,
thanks for the hints. The macro works good. The patch is attached.
(I will never use HPGL, and don't give a crap about it. If somebody just
wants to fix it,
go ahead.
Many old pen plotters use only HPGL. They can coat directly the PCB
On 01/25/2013 04:08 PM, Brian Sidebotham wrote:
> I think this is worthy of another new thread, but is a fork of the Python
> Scripting
> cmake build macros. There are some notes on using MinGW with msvcr90.dll as a
> target C
> runtime.
>
> I added a new specs file to my local KiCad MinGW instal
I think I found an annoying improvement...
In pcbnew, when moving a module (i.e. the M key) the origin is not
snapped anymore to the grid, i.e. the grid only gives the movement
steps, not the absolute position. Was that wanted?
The annoying part is this: I have a board designed in metric, so most
On 4 February 2013 02:19, Dick Hollenbeck wrote:
> Success seems *highly* likely now. Even with success, it will need to be
> a team effort,
> since I probably cannot be expected to maintain this work. (Maintenance
> means moving the
> unaccepted portions forward to newer versions of python.)
>
9 matches
Mail list logo
