Thanks Jon - I don't have access to Altium so that's really helpful.
I was wondering about the possibility of locking components; I sometimes
want to do this with, for example, key ICs - MCUs, DACs, etc. One could add
this as a Symbol Property, which wouldn't need any changes to file formats.
Altium doesn't have "annotate selected"
It does let you lock the annotation on components at will, so you can lock
some, reset everything (which ignores locked) and then re-annotate.
If you change the annotation of one part of a multi-part component, it will
result in two components being
That's an interesting take on it. I can foresee the catastrophic addition
of loads of other components though, if there's an error in the schematic
somewhere and a rogue missing / one-over unit gets cascaded down sheets.
What do other EDA tools do with annotation? Do they have this feature? Do
Thanks Jeff - I'll take a look at a nightly to see where things are now.
Sounds like a much better selection strategy too!
Jean-Pierre - You're quite right to highlight these complications, which
I've been mulling over myself. I don't yet have proposed solutions, but I'm
going to give it a good
Le 07/05/2020 à 20:15, Jeff Young a écrit :
> Hi James,
>
> You might first want to download one of the nightlies (5.99) and play with
> it. Block selections are gone: eeschema now has a “normal” selection model
> where you click on things and/or drag-select and they get highlighted.
>
> So
Hi James,
You might first want to download one of the nightlies (5.99) and play with it.
Block selections are gone: eeschema now has a “normal” selection model where
you click on things and/or drag-select and they get highlighted.
So from the GUI perspective you’d just need to add the options
You heard it here first: not a tentative plan, a definite plan :) (or at
least as definite as these things get)
Project format will be changing, and the extension will change to kicad_pro
along with it.
The extension change will not apply to the existing file format.
This change is tied to other
It's on my TODO list, it will happen as part of a new project format
https://gitlab.com/kicad/code/kicad/-/issues/2169
-Jon
On Thu, May 7, 2020 at 12:18 PM Wayne Stambaugh
wrote:
> I'm pretty sure this has been discussed to death but but until a new
> project file format is created, the file
I'm pretty sure this has been discussed to death but but until a new
project file format is created, the file extension will remain .pro.
It's bad enough that this clashes with other applications but having an
internal file format clash just fix something unrelated to KiCad doesn't
make much sense
There is a tentative plan to change this to a `.kicad_pro` file in v6, but
it hasn't been completely thought through yet. See
https://gitlab.com/kicad/code/kicad/-/issues/2169#note_286814996.
-Ian
On Thu, May 7, 2020 at 5:05 PM RigoLigo RLC wrote:
> Hello everyone,
>
> The .pro project file
Hello everyone,
The .pro project file extension might be a historical problem, but I really
should mention that this extension was used by too many programs, for
example, Qt Creator.
Now the kicad_sch extension came with the S-expression style schematics
format, I'd like to ask would KiCad plan
github for now
tor. 7. maj 2020 15.55 skrev Wayne Stambaugh :
> I just made some changes to the blog post to reflect a code change. Are
> we still using the GitHub repo or have we migrated the website to the
> GitLab repo?
>
> On 5/6/20 10:59 PM, Mark Roszko wrote:
> > I made it better, maybe
>
Brian,
Great to know that I'm not the only one who thought it a useful addition.
Really happy to collaborate, and to try and unpick those issues. As I'm not
the KiCad dev it'll take me a little while to figure out the code flow, but
no harm in having a crack. Great if you were able to bring your
I just made some changes to the blog post to reflect a code change. Are
we still using the GitHub repo or have we migrated the website to the
GitLab repo?
On 5/6/20 10:59 PM, Mark Roszko wrote:
> I made it better, maybe
>
> On Wed, May 6, 2020 at 6:00 PM Nick Østergaard
Hello James
I had been working on this for some time and ran into a brick wall so I
set it aside.
There seems to be an issue with the structures used within eeSchema
(sheets, screens, etc.) which don't seem to consistently track UUIDs,
etc. I suspect that this may be because eeSchema
Hi all,
Firstly thanks Wayne for adding me to the list - long time KiCad user for
hobby stuff, but I've got a background (partially) in fast real-time
mixed-signal electronics.
Working on a fairly large personal project recently, with many nested and
shared schematics, I would really have liked
Awesome, thanks!
tor. 7. maj 2020 04.59 skrev Mark Roszko :
> I made it better, maybe
>
> On Wed, May 6, 2020 at 6:00 PM Nick Østergaard wrote:
>
>> I have done it, could't be bothered with the bullet points though. :)
>>
>> On Wed, 6 May 2020 at 23:11, Wayne Stambaugh
>> wrote:
>> >
>> > If
17 matches
Mail list logo
