Ohh, you mean in the legacy canvas. Also I noticed some
inconsistencies with the renders. When moving track segment in legacy
it will be "detached" from the net, but in GAL it the restnest will
still include the loose track segment. (I have not tried your patch
yet)
2015-05-13 22:26 GMT+02:00 Ni
On 5/13/2015 4:28 PM, Nick Østergaard wrote:
> 2015-05-13 21:22 GMT+02:00 Wayne Stambaugh :
>> I'm not sure why swapped pins in the system libraries would be an issue
>> since the cached components should product the correct schematic.
>> Assuming the rescue library is properly fetching the compone
2015-05-13 21:22 GMT+02:00 Wayne Stambaugh :
> I'm not sure why swapped pins in the system libraries would be an issue
> since the cached components should product the correct schematic.
> Assuming the rescue library is properly fetching the components from the
> cache library, I can't see how any
I can't seem to reproduce this bug on 5645. When I use the right
click context menu for a track segment or a footprint in pcbnew the
rastnest is updated accordingly.
2015-05-13 20:30 GMT+02:00 Joel Matějka :
> Hi,
>
> I haven't specified this patch enough. When you move a segment (or a pad) by
>
My 10.10/10.10 build just finished. I am debugging Python things, hoping
to get that pushed over to mainline for the nightlies.
I still cannot get 10.7 builds working on my 10.10.3 machine, and it's very
concerning to me. I'll try 10.9 and 10.8. For a year or so now, XCode no
longer includes th
> On May 13, 2015, at 10:27 AM, Bernhard Stegmaier
> wrote:
>
> Hi,
>
> I made successfully some builds last weekend… after I sorted out the cmake
> problems with using a non-system openssl I have posted.
> I always use external boost from MacPorts (just like all other dependencies)
> at lea
I found another schematic with the same problem. The changed zener
diode is not getting detected or at least for me it doesn't show up in
the list of components to rescue. Perhaps there is a bug in the
component comparison code. It may be the LIB_PIN comparison is the
issue. You should be able
I'm not sure why swapped pins in the system libraries would be an issue
since the cached components should product the correct schematic.
Assuming the rescue library is properly fetching the components from the
cache library, I can't see how any changes in the system libraries would
cause this. Un
Hi,
I haven't specified this patch enough. When you move a segment (or a pad) by
specifying offset in move exactly function in on right click menu, the
segment is moved, but rats nest is not recalculated (not shown new
disconnection). When you click undo and redo, rats nest is shown correctly.
Thanks for the info.
(Also, I think my 10.10/10.10 build is going through now at least.)
Adam Wolf
On Wed, May 13, 2015 at 12:27 PM, Bernhard Stegmaier <
stegma...@sw-systems.de> wrote:
> Hi,
>
> I made successfully some builds last weekend… after I sorted out the cmake
> problems with using a
Hi,
I made successfully some builds last weekend… after I sorted out the cmake
problems with using a non-system openssl I have posted.
I always use external boost from MacPorts (just like all other dependencies) at
least half a year now… 1.56 and after the MacPorts update 1.58.
I didn’t rebuild
Hi folks,
The nightly OS X builds are continuing fine.
I am debugging some issues on my development machine.
Who is able to make a Mac build, and what version of XCode are you running?
The issues I'm having are mismatches between wx and boost and kicad. When
I build for 10.7 on 10.10, like I d
I don't use the KiCad libraries usually, so I'm unaware - were the pin numbers
swapped? If that's the case, I'm not sure of a way to handle that gracefully,
as from the software's perspective, pin 1 is pin 1 is pin 1 - the fact that the
cathode band is drawn elsewhere obviously doesn't factor i
This is altogether possible as I have recently installed the latest
library changes.
On 5/13/2015 11:37 AM, Maciej Sumiński wrote:
> Is it possible the problem is related to the recent diode pin swapping
> in KiCad library?
>
> Regards,
> Orson
>
> On 05/13/2015 05:35 PM, Chris Pavlina wrote:
>>
Is it possible the problem is related to the recent diode pin swapping
in KiCad library?
Regards,
Orson
On 05/13/2015 05:35 PM, Chris Pavlina wrote:
> Hi Wayne,
>
> That's interesting. I can't really imagine what would cause that, and I
> haven't seen anything like that - I've tested it on many
Hi Wayne,
That's interesting. I can't really imagine what would cause that, and I haven't
seen anything like that - I've tested it on many projects that should have
stirred that bug up if it existed. Any chance you can share with me the problem
project?
Chris
On Wed, May 13, 2015 at 11:01:1
Patch committed in product branch r5653. Thank you for you contribution.
On 5/4/2015 1:30 PM, Chris Pavlina wrote:
> I've got two changes here - they're a bit inadvertently intertwined, so
> I left them as one patch, otherwise one would depend on the other
> anyway. Let me know if you want me to
Chris,
I just tested this and I like the changes. I believe I found a bug. I
just rescued an old project and noticed all of the zener diodes were
oriented 180 degrees from the unrescued version. When you get a chance,
would you please verify the component orientation against the rescued
library
Blair,
I was looking at this patch and I like the idea of entering arc angles
in degrees instead of deci-degrees. I'm sure most users will appreciate
it. However, the wxSpinCtrl hack needs to be replaced by using a
wxSpinCtrl when creating the dialog with wxFormBuilder. wxFormBuilder
v3.5 suppo
When pcbnew imports a eagle PCB, with a old number of copper layers, it
works fine, and save's the result with out any
error's
But when you open the now saved kicad-pcb file it says you have invalided
copper layer count.
I'm not quite sure, if this a valid assumption, as there is no reason yo
20 matches
Mail list logo
