Has anyone else looked at this patch? If you haven't, it adds a select
button that launches the footprint viewer to select a footprint to the
edit field properties dialog when the footprint field is selected. I
personally like it but since it's behavioral change I would like some
input before I
Sorry, I didn't get much chance to look at it - but I liked the idea
of it - I think this is one of the very reasons behind the KiWay work.
It's certainly a bonus of that work which we should be reaping.
I didn't get a chance to apply and test though. Let me know if you need that.
Best Regards,
I've already applied the patch to my branch and did some testing. It
works as advertized but I just want to make sure we are for the most
part on board with the changes. I'll wait a while to make sure there
are no strong objections before I commit the changes. Thanks for the
feedback.
Cheers,
On Oct 14, 2014, at 6:58 AM, Wayne Stambaugh stambau...@verizon.net wrote:
Has anyone else looked at this patch? If you haven't, it adds a select
button that launches the footprint viewer to select a footprint to the
edit field properties dialog when the footprint field is selected. I
Le 13/10/2014 16:51, Carl Poirier a écrit :
Benoît, this is exactly what I tried to say. I wasn't talking about
symbols in Altium, but about components.
They are already associated with footprints and so on, thus making
them components.
They can be not associated and still used...
Here a
I forgot about this patch, but I have now applied it and do not see
any issue with it. I cannot comment on the code.
But while testing it out I noticed that above the textbox it just says
Text in a label. Shouldn't this be Footprint name or something
similar?
Nick
2014-10-14 17:24 GMT+02:00
On 10/14/2014 1:30 PM, Nick Østergaard wrote:
I forgot about this patch, but I have now applied it and do not see
any issue with it. I cannot comment on the code.
But while testing it out I noticed that above the textbox it just says
Text in a label. Shouldn't this be Footprint name or
2014-10-14 19:57 GMT+02:00 Wayne Stambaugh stambau...@verizon.net:
On 10/14/2014 1:30 PM, Nick Østergaard wrote:
I forgot about this patch, but I have now applied it and do not see
any issue with it. I cannot comment on the code.
But while testing it out I noticed that above the textbox it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have briefly tested it and read the patch. No issues came to my mind,
but I am not very familiar with eeschema code. I like the change in
the eeschema behaviour as well - good job!
Regards,
Orson
On 10/14/2014 03:58 PM, Wayne Stambaugh wrote:
Has
Thanks Orson. I think this patch will be well received so I'm going to
go ahead and commit it.
Wayne
On 10/14/2014 4:19 PM, Maciej Sumiński wrote:
I have briefly tested it and read the patch. No issues came to my mind,
but I am not very familiar with eeschema code. I like the change in
the
On 13 October 2014 17:22, Wayne Stambaugh stambau...@verizon.net wrote:
On 10/12/2014 9:14 PM, Mark Roszko wrote:
Very minor but the main KiCAD window calls it Schematic Library
Editor, eeschema calls it Library Editor and the window itself is
Parts Library Editor.
Can the name be
Hey Mark,
I just committed this patch to r5188 of the product branch. Thank you
for you contribution to KiCad. I do have a few comments.
1) Doxygen comments do not belong in the source file. They belong in
the header file. I moved them this time.
2) There was some trailing whitespace.
3)
The manual uses component throughout and indeed Component name in the UI
Component properties dialog. All the screenshots show Component too.
If eeschema has changed these, they should be changed back
An manual should never define the software, it should explain the
software. Or else we'll never
On 14 October 2014 21:54, Mark Roszko mark.ros...@gmail.com wrote:
The manual uses component throughout and indeed Component name in the UI
Component properties dialog. All the screenshots show Component too.
If eeschema has changed these, they should be changed back
An manual should never
On 10/14/2014 4:43 PM, Brian Sidebotham wrote:
On 13 October 2014 17:22, Wayne Stambaugh stambau...@verizon.net wrote:
On 10/12/2014 9:14 PM, Mark Roszko wrote:
Very minor but the main KiCAD window calls it Schematic Library
Editor, eeschema calls it Library Editor and the window itself is
On 14 October 2014 21:57, Brian Sidebotham brian.sidebot...@gmail.com wrote:
On 14 October 2014 21:54, Mark Roszko mark.ros...@gmail.com wrote:
The manual uses component throughout and indeed Component name in the UI
Component properties dialog. All the screenshots show Component too.
If eeschema
Be it just semantics but for me
Documentation != Manual != Specifications
A specification defines the feature, behaviors, etc. This is written
ahead of time.
A manual is for end users in a descriptive and easy to read form to follow.
Documentation is for developers to understand what is going on
On 14 October 2014 22:16, Mark Roszko mark.ros...@gmail.com wrote:
Be it just semantics but for me
Documentation != Manual != Specifications
It is probably just semantics, but then this is wrong because
apparently Documentation != Manual !?
I wish the manuals were plain text based, I would
FYI, latest code is sitting in merge proposal
https://code.launchpad.net/~mark-roszko/kicad/hotkey/+merge/238225
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe :
On 14 October 2014 22:09, Mark Roszko mark.ros...@gmail.com wrote:
Ah, the only thing that changed is I moved all the comments from the
.cpp to .h as you asked before so you can't ding me for that :P And a
description.
There is a white space line I just noticed.
I am having trouble with
Well, going back to what the manual states it was before is indeed a good
point.
If this is the final decision, I'll update the library convention.
On Tue, Oct 14, 2014 at 5:20 PM, Brian Sidebotham
brian.sidebot...@gmail.com wrote:
On 14 October 2014 22:16, Mark Roszko mark.ros...@gmail.com
On 10/14/2014 5:09 PM, Mark Roszko wrote:
Ah, the only thing that changed is I moved all the comments from the
.cpp to .h as you asked before so you can't ding me for that :P And a
description.
There is a white space line I just noticed.
Not a problem. I thought I that was the latest version
On 10/14/2014 4:54 PM, Mark Roszko wrote:
The manual uses component throughout and indeed Component name in the UI
Component properties dialog. All the screenshots show Component too.
If eeschema has changed these, they should be changed back
An manual should never define the software, it
I have emailed out a patch for kicad-install.sh, which will fix the problem
you encountered.
--Joe
On Monday, October 13, 2014 12:14 AM, Benoît Roehr
benoit.roehr...@gmail.com wrote:
Finally succesfully build kicad on a all fresh Ubuntu 14.04 yesterday.
apt-get build-dep kicad
I'm leaning towards one of the markdown formats myself.
I vote for markdown :D
In fact, here, I ran a quick convert of ODT to markdown and imported
it into a gitbook setup. Here's chapter 1 and 2 being served from
markdown and combined with Gitbook and then being served from a git
repo via
25 matches
Mail list logo
