On 10/11/2016 12:18 AM, Strontium wrote:
> On 11/10/16 09:27, Wayne Stambaugh wrote:
>> I've thought about this for a while and I'm going to try a different
>> approach. Please bear with me, this is going to be lengthy but in the
>> interest of resolving the via stitching issue properly, I think
Le 11/10/2016 à 09:03, John Devereux a écrit :
> Strontium writes:
>
>> On 11/10/16 09:27, Wayne Stambaugh wrote:
>
> [...]
>
>>
>>>I can't think of any valid case
>>> where you would want unconnected (floating) or partially connected (1
>>> connection) vias or vias
Fyi. To confirm your statement, Windows chooses default paper based on
locale too.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More
Hi,
At least on Linux, and probably on other platforms, the system locale
specifies the standard local paper size. Can anybody explain to me,
then, why sch_screen.cpp:98 hard codes this to A4? KiCad is a localized
application, surely the developer who daydreamed of the entire world
using A4 by
On 10/11/2016 2:09 PM, Chris Pavlina wrote:
> Hi,
>
> At least on Linux, and probably on other platforms, the system locale
> specifies the standard local paper size. Can anybody explain to me,
> then, why sch_screen.cpp:98 hard codes this to A4? KiCad is a localized
> application, surely the
On my Macbook Air, the page size default seems to come from
SystemPreferences->Printers & Scanners->Default paper size (menu list
including A4 and US letter - at the bottom of panel)
When I come back from Europe, it usually takes me awhile to remember to
change this. It does not set itself.
When in doubt show distinguishing table.
But why not do to it for user as simple as:
1. select via tool
2. set via parameters (drill diameter, annular ring or set from net or
zone automaticaly)
3. place via
3.1. when user moving over board with via tool then
- when user set
And people argue with me when I say Boost is a piece of crap.
On Tue, Oct 11, 2016 at 07:38:59PM -0400, Wayne Stambaugh wrote:
> Another boost version, another broken context switching build. Has
> anyone successfully built kicad against boost 1.62? The msys2 project
> just packaged 1.62 and
Can't reproduce on windows with msvc + 1.62 (tried that weeks ago with
an rc already). Might be an msys, mingw or gcc thing. Any hints to what
causes this?
Michael
Am 12.10.2016 um 02:54 schrieb Chris Pavlina:
And people argue with me when I say Boost is a piece of crap.
On Tue, Oct 11,
Another boost version, another broken context switching build. Has
anyone successfully built kicad against boost 1.62? The msys2 project
just packaged 1.62 and kicad fails to build on windows. If you haven't
upgraded yet, don't. Otherwise you will to downgrade. Hopefully this
saves someone
On 11/10/16 23:35, Wayne Stambaugh wrote:
On 10/11/2016 12:18 AM, Strontium wrote:
On 11/10/16 09:27, Wayne Stambaugh wrote:
I've thought about this for a while and I'm going to try a different
approach. Please bear with me, this is going to be lengthy but in the
interest of resolving the
Hi everybody,
Attached there is a patch to add the save function for the configuration
of the print dialog.
Often I need to generate prints from combined layers to have documents
for production and selecting every time the right combination of layers
and features is error prone and
Strontium writes:
> On 11/10/16 09:27, Wayne Stambaugh wrote:
[...]
>
>>I can't think of any valid case
>> where you would want unconnected (floating) or partially connected (1
>> connection) vias or vias that short different nets together. If you can
>> think of one,
13 matches
Mail list logo