On Sun, Mar 22, 2015 at 03:11:30PM +0100, jp charras wrote:
> These hotkey strings info are now translated in dialogs in rev 5530.
Many thanks! Starting translating right now!
PS:
#: pcbnew/hotkeys.cpp:96
msgid "Save Module"
is this right or you meant a "Save footprint"?
--
Marco Ciampa
I k
Le 23/03/2015 08:51, Marco Ciampa a écrit :
> On Sun, Mar 22, 2015 at 03:11:30PM +0100, jp charras wrote:
>> These hotkey strings info are now translated in dialogs in rev 5530.
>
> Many thanks! Starting translating right now!
>
> PS:
>
> #: pcbnew/hotkeys.cpp:96
> msgid "Save Module"
>
> is th
Le 22/03/2015 11:45, Mário Luzeiro a écrit :
> Hi all,
>
> While working in 3D-Viewer, I found something that I am not sure if is an
> issue or feature.
>
> It seems that the Non plated TH PAD types are extracted the way you can see
> in the attached picture. I was expecting no copper at all, b
Le 22/03/2015 16:42, Mário Luzeiro a écrit :
> Hello all,
> Does anyone have a test project (for pcbnew) that I can use to test and see
> several complex aspects in a board?
> Things like multi layers, complex edge cuts, different holes shapes and
> sizes, complex filling zones.. etc etc?
>
> Th
Le 22/03/2015 22:24, Michele Ballabio a écrit :
> From: Michele
>
> There are two Hotkey submenu under "Preferences" in Kicad.
> This patch removes the second one.
>
> ---
> kicad/menubar.cpp | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/kicad/menubar.cpp b/kicad/menubar.cpp
> ind
On Mon, Mar 23, 2015 at 09:29:37AM +0100, jp charras wrote:
> I mean "Save Footprint"
> Modified in rev 5531.
Thanks!
During translation you encounter many small typo and such, it is like an
involuntary revision.
Perhaps here there is another:
#: pcbnew/pad_edition_functions.cpp:217
#, c-format
Le 23/03/2015 04:25, Chris Pavlina a écrit :
> Got it - fixed. Looks like I was a bit overzealous in correcting the
> first patch and introduced this.
>
> I also found another issue - it didn't treat unannotated parts
> differently, so if you had a schematic full of R?A it would try to make
> them
Le 23/03/2015 05:20, Chris Pavlina a écrit :
> Currently, if you try to edit the value of a power component in
> eeschema, you get a "... is a power component and it's [sic] value
> cannot be modified!" message. That message isn't completely accurate,
> though. The edit box also allows you to chan
When loading an old schematic, it's fairly common for it to be broken,
if symbols have changed significantly in the libraries. An example:
https://i.imgur.com/7cVBneA.png
A workaround suggested by Wayne is to make a local copy of the
projname-cache.lib file, and add it to the project as a libr
A quick note to our library developers. I really like some of the
recent work you have been doing. It would be nice in the future when
you make big changes like renaming files and paths to give everyone a
heads up on developers mailing list and possibly the users mailing lists
so we don't get bli
Hi!
That is unfortunate. I really would like this: use the cached version, unless
you choose to update from library (in a global menu, or per component). This
is
really handy, since you don't have to do anything, unless you specifically want
to (for example, there is a new, better symbol), an
I like your idea - I proposed it myself, but it was not well received ;)
(Bah, still getting used to the fact that Launchpad doesn't set reply-to)
On Mon, Mar 23, 2015 at 05:06:08PM +0100, Ladislav Laska wrote:
Hi!
That is unfortunate. I really would like this: use the cached version, unless
y
On 3/23/2015 12:12 PM, Chris Pavlina wrote:
> I like your idea - I proposed it myself, but it was not well received ;)
>
> (Bah, still getting used to the fact that Launchpad doesn't set reply-to)
>
> On Mon, Mar 23, 2015 at 05:06:08PM +0100, Ladislav Laska wrote:
>> Hi!
>>
>> That is unfortunate
On Mon, Mar 23, 2015 at 01:07:33PM -0400, Wayne Stambaugh wrote:
On 3/23/2015 12:12 PM, Chris Pavlina wrote:
I like your idea - I proposed it myself, but it was not well received ;)
[[snip]]
Please see the discussion here on why this will not work.
https://bugs.launchpad.net/kicad/+bug/143533
On 3/23/2015 1:16 PM, Chris Pavlina wrote:
> On Mon, Mar 23, 2015 at 01:07:33PM -0400, Wayne Stambaugh wrote:
>> On 3/23/2015 12:12 PM, Chris Pavlina wrote:
>>> I like your idea - I proposed it myself, but it was not well received ;)
>>> [[snip]]
>>
>> Please see the discussion here on why this wil
Hello,
I would like to propose a tool "via stitching". Simply many via next to
each other.
Via stitching is required for me to do thermal transfer from one side to
the other. Manual placing requires a lot of effort, a tool could
simplify that.
Usage: I would to specify the area and the net a
Hi everyone.
Let me express few words about changes in the symbol libraries.
At the moment there are no major changes in the naming of the
current symbol library files. Together with GitHub users we added
and we are planning to add a few new ones.
One library is provided for the liquidation in
KiCad does not currently support standalone vias, and I think that would
be a necessity before a *clean* implementation of this could be done.
The only other options are to either place a /footprint/ as a via
(nasty), or place a web of traces along with the vias (terribly,
horribly filthy).
T
I'm getting close to finishing up the environment variable editing
dialog and I'm struggling with the best option to set variables that
have already been define outside the currently running process. Here
are the options that I see:
1) Set all environment variables to the values defined in the di
For people who want to follow any change in library, Github allow to watch a
repo:
> When you watch a repository, you get notifications (by email) for any new
> pull
> requests and issues that are created, including those not mentioning you.
https://help.github.com/articles/watching-repositori
#1 works slightly better for normal users for OS X, if I'm understanding
you correctly.
Adam Wolf
Cofounder and Engineer
W&L
On Mon, Mar 23, 2015 at 1:36 PM, Wayne Stambaugh
wrote:
> I'm getting close to finishing up the environment variable editing
> dialog and I'm struggling with the best opt
It should work better for users on all platforms except if they have
already set the environment variables externally (as we ask them to do
before I added the default settings or they used one of the kicad source
build and install scripts) and they forget to remove them before using
the new configu
> On Mar 23, 2015, at 10:56 AM, Chris Pavlina wrote:
>
> KiCad does not currently support standalone vias, and I think that would be a
> necessity before a *clean* implementation of this could be done. The only
> other options are to either place a /footprint/ as a via (nasty), or place a
> w
Hi,
Am 23.03.2015 um 18:56 schrieb Chris Pavlina:
> KiCad does not currently support standalone vias, and I think that would
> be a necessity before a *clean* implementation of this could be done.
I think these vias would be placed inside a copper pour, so there is
something to "connect" them to
On 3/23/2015 3:25 PM, Simon Richter wrote:
> Hi,
>
> Am 23.03.2015 um 18:56 schrieb Chris Pavlina:
>
>> KiCad does not currently support standalone vias, and I think that would
>> be a necessity before a *clean* implementation of this could be done.
This would have to be done first and it would
Le 23/03/2015 12:01, Mário Luzeiro a écrit :
> Hello all,
> here are my new contribution for the 3d-viewer.
>
>
> I feel that I cannot do or think in any major improvements to 3d-viewer in
> the way it is now.
> I think that changes must be done in the 3d-viewer architecture and
> integration w
Le 23/03/2015 20:28, Wayne Stambaugh a écrit :
> On 3/23/2015 3:25 PM, Simon Richter wrote:
>> Hi,
>>
>> Am 23.03.2015 um 18:56 schrieb Chris Pavlina:
>>
>>> KiCad does not currently support standalone vias, and I think that would
>>> be a necessity before a *clean* implementation of this could be
I will! I missed a bit that overall evaluation of the coding policy.
MRL
From: jp charras [jp.char...@wanadoo.fr]
Sent: 23 March 2015 20:48
To: Mário Luzeiro; kicad-developers@lists.launchpad.net
Subject: Re: 3d viewer updates
Le 23/03/2015 12:01, Mário Lu
It seems like option #1 is the saner option.
If I’m understanding the change, once the variables are edited they become
configuration variables. Typical precedence for configuration is usually
something like, command line -> environment -> local config files -> global
config files, from highe
I agree with Wayne,
I watch the repositories, but I barely have the time to track all the
discussions.
So I join his request, if some of those discussions could affect a lot of people
using the parts, please bring it to the development list.
Looking into the future, it would be awesome if at
Le 23/03/2015 22:44, Garth Corral a écrit :
>
> It seems like option #1 is the saner option.
>
> If I’m understanding the change, once the variables are edited they
> become configuration variables. Typical precedence for configuration
> is usually something like, command line -> environment ->
31 matches
Mail list logo
