Hi Reece-
I've had a chance to test this a bit. It works really nicely. Thanks
for the good idea here.
I only noticed one spot where it wasn't transformed so far: the
Measurement tool. When used, it displays a sign with the distance,
which doesn't match the increasing/decreasing
Hi,
Am 24/05/2019 um 13:32 schrieb Wayne Stambaugh:
Just as an FYI in case it wasn't obvious, Seth's proposal uses library
IDs to define the symbol and footprint.
Yes, so would mine, on any level that is more detailed than "footprint".
The main problem I see with atomic libraries is that
Great idea! I have a lightweight test procedure for macOS packaging of
major releases here, under Test Procedure:
https://github.com/KiCad/kicad-mac-builder/blob/master/README.md
On Sat, May 25, 2019 at 11:27 AM Seth Hillbrand wrote:
>
> Hi Devs-
>
> I've committed a proposed checklist format
Hi Devs-
I've committed a proposed checklist format to my branch[1] on launchpad.
This is the outline of a proposed checklist for KiCad releases that we
can use to verify consistent (i.e. fewer regressions) behavior before
tagging new versions. This currently documents just the main window.
The Zip file attachment contains the complete set of patches
implementing Display Origin Transforms, now squashed and rebased for
your merging pleasure!
They should apply cleanly atop this commit from JP Charras:
b8e2054 Activate context menu in LIB_VIEW_FRAME canvas.
Folks, please resist
Le 19/05/2019 à 21:28, jp charras a écrit :
> Le 18/05/2019 à 14:13, Tomasz Wlostowski a écrit :
>> On 13/05/2019 12:58, jp charras wrote:
>>> If we are talking about V6.0 version, we should add zone property field
>>> in the file format like (outline_thickness 0.0) to avoid serious issues
>>>
6 matches
Mail list logo
