Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
K
kicad-source-mirror
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Commits
Open sidebar
Elphel
kicad-source-mirror
Commits
1ff2b559
Commit
1ff2b559
authored
Jun 17, 2010
by
Dick Hollenbeck
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Forgot to give Brian credit
parent
a6cbee35
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
1 deletion
+5
-1
CHANGELOG.txt
CHANGELOG.txt
+5
-1
No files found.
CHANGELOG.txt
View file @
1ff2b559
...
@@ -7,7 +7,11 @@ email address.
...
@@ -7,7 +7,11 @@ email address.
2010-Jun-17 UPDATE Dick Hollenbeck <dick@softplc.com>
2010-Jun-17 UPDATE Dick Hollenbeck <dick@softplc.com>
================================================================================
================================================================================
++eeschema:
++eeschema:
Added "template fieldnames" to eeschema. This is a list of template elements
Added "template fieldnames" to eeschema. Thanks to
Brian Sidebotham <brian.sidebotham@gmail.com> for the origins of this patch.
https://lists.launchpad.net/kicad-developers/msg04828.html
A template fieldnames are a list of template elements
consisting of {name, value, visibility} which you want shown in the eeschema
consisting of {name, value, visibility} which you want shown in the eeschema
component fieldname (property) editors (both schematic and library versions
component fieldname (property) editors (both schematic and library versions
of the editors). Template fieldnames are forced into the editors'
of the editors). Template fieldnames are forced into the editors'
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment