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
61454f01
Commit
61454f01
authored
Feb 21, 2008
by
CHARRAS
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
eeschema: problem when undelete after a change a label type solved (I hope)
parent
1d16eae0
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
7 additions
and
3 deletions
+7
-3
change_log.txt
change_log.txt
+1
-2
edit_label.cpp
eeschema/edit_label.cpp
+6
-1
No files found.
change_log.txt
View file @
61454f01
...
...
@@ -14,8 +14,7 @@ email address.
- reference not copied in component copy.
- incorrect redo when changing the chip name in component edition
bugs not fixed
- undo/redo problems when changing a text type between text, label, global label and hierarchical label
bugs not fixed:
- incorrect annotation in complex hierarchy with multi parts per package (duplicates created).
...
...
eeschema/edit_label.cpp
View file @
61454f01
...
...
@@ -396,7 +396,8 @@ void WinEDA_SchematicFrame::ConvertTextType( DrawTextStruct* Text,
GetScreen
()
->
SetCurItem
(
NULL
);
g_ItemToRepeat
=
NULL
;
}
GetScreen
()
->
SetCurItem
(
newtext
);
GetScreen
()
->
SetCurItem
(
NULL
);
SAFE_DELETE
(
g_ItemToUndoCopy
);
...
...
@@ -412,11 +413,15 @@ void WinEDA_SchematicFrame::ConvertTextType( DrawTextStruct* Text,
SaveCopyInUndoList
(
newtext
,
IS_NEW
);
}
else
{
GetScreen
()
->
SetCurItem
(
newtext
);
newtext
->
m_Flags
=
IS_NEW
;
}
if
(
(
flags
&
IS_MOVED
)
!=
0
)
{
GetScreen
()
->
SetCurItem
(
newtext
);
StartMoveTexte
(
newtext
,
DC
);
}
...
...
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