I did some testing and the changes appear to have resolved the original
issues I found. One thing I did not test was complex hierarchical bus
expansion. Has anyone else tested this yet? I hope to get to it over
the weekend. It's definitely something that should be tested before we
give it our
Am 2019-03-22 16:51, schrieb Seth Hillbrand:
adjust but I'm seeing show stoppers.
** not ** seeing show stoppers.
-S
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe :
I don't quite follow - what I'm proposing doesn't require any file
format changes, I was planning to just use the existing field functionality.
If you want to bake it into the format instead, I'm 100% okay with that,
but I don't think it's necessary. I'll look into implementing the UI
Just a reminder that KiCon[1] is just over a month away so if you didn't
get your tickets yet, please head over the KiCon website to register.
Do not wait to the last minute if you don't have to. It helps the
organizers with planning if they have an accurate head count in advance
for planning for
Am 2019-03-12 17:11, schrieb Jon Evans:
https://code.launchpad.net/~craftyjon/kicad/+git/kicad/+merge/364346
On Tue, Mar 12, 2019 at 4:32 PM Seth Hillbrand
wrote:
Am 2019-03-11 18:03, schrieb Jon Evans:
Rebased branch is located here:
Hi Kliment
This cannot happen until the new symbol library file format is
implemented. There is a freeze (except for the new bus expansion
changes) on the current file format. I will add a unit description
field for units in the new file format this way you can add a unique
description for each
Wayne
I think I understand. The problem is that at maximum zoom the grid shows 10
mill, not 1 mill, which makes it very difficult to actually move the cursor
to a particular spot.
Perhaps it might be useful to flash a warning if somebody tries to set the
grid to less than 10 mill in eeSchema, in
Brian
On 3/22/2019 12:32 PM, Brian Piccioni wrote:
> From a position of (mostly) ignorance, isn't the real question
>
> "how can things be off-grid in a system where all the coordinates are
> expressed in whole numbers"?
>
> I looked at the test file
>
Le 22/03/2019 à 15:03, Tomasz Wlostowski a écrit :
> On 22/03/2019 13:43, Wayne Stambaugh wrote:
>> Tom,
>>
>> AFAIR, the cursor position was always used in order to keep everything
>> on grid. Since there has never been connection snapping in Eeschema,
>> the grid is the only way to ensure
On 22/03/2019 13:43, Wayne Stambaugh wrote:
> Tom,
>
> AFAIR, the cursor position was always used in order to keep everything
> on grid. Since there has never been connection snapping in Eeschema,
> the grid is the only way to ensure connections.
Hi Wayne,
I want to use mouse position only to
Tom,
AFAIR, the cursor position was always used in order to keep everything
on grid. Since there has never been connection snapping in Eeschema,
the grid is the only way to ensure connections.
Cheers,
Wayne
On 3/21/19 7:41 PM, Tomasz Wlostowski wrote:
> Hi all,
>
> In the thread [1] on the
Hey,
I'm working with a part that has a very large number of
non-interchangeable units, each with many pins. For a part like this,
it's very difficult to tell which unit is which from the preview. Parts
have a description field that is shown in the list, but units don't. For
parts with
Tomasz Wlostowski kirjoitti 22.3.2019 klo 1.41:
> willing to fix this. Editing a schematic with non-aligned pins is now
> next to impossible...
It has never been possible...
https://lists.launchpad.net/kicad-developers/msg26704.html
I would be very happy to see it fixed.
-Vesa
On 22.03.2019 01:41, Tomasz Wlostowski wrote:
Is there a chance there's a regression in V5/V5.1? If so, I'm
willing to fix this.
Does it need to be a regression to be fixed?
--
Regards,
Sergey A. Borshchmailto: sb...@sourceforge.net
SB ELDI ltd. Riga, Latvia
14 matches
Mail list logo
