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
b589bca9
Commit
b589bca9
authored
Nov 04, 2007
by
dickelbeck
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
todo.txt update
parent
fba04618
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
28 additions
and
0 deletions
+28
-0
todo.txt
todo.txt
+28
-0
No files found.
todo.txt
View file @
b589bca9
...
@@ -55,3 +55,31 @@ understanding by new developers.
...
@@ -55,3 +55,31 @@ understanding by new developers.
*** Add tooltip text to all non-obvious controls in every dialog window.
*** Add tooltip text to all non-obvious controls in every dialog window.
Need to do this using DialogBlocks.
Need to do this using DialogBlocks.
2007-Nov-4 Assigned To: dick, but probably not til January.
================================================================================
Enhance DRC dialog box to:
1) retain lines of error text, so as user re-enters dialog, the previously found errors persist.
2) support double or single clicking a text line, and have the pcbnew cursor go to the offending marker.
3) use color in the text line display.
4) use tooltip on a per line basis, which would show a generic, but error type specific
message about the error for that line.
5) Use sizers properly so that as the dialog box is resized, the text area gets
all the additional space, both horizontally and vertically.
6) The initial size of the dialog needs to be big enough to show the text lines
in a clear way.
7) Add a delete button so user can remove a single line of text after he fixes that track. The delete button
should also delete that single marker.
--------------
Implementation Ideas: retain all drc wxStrings in a vector<wxString> so they
can be re-displayed again on another popup of the dialog. Switch from wxTextControl
to wxHtmlListBox for the errors. Add parsing and formatting functions to allow
grabbing of the coordinate of the marker out of text, and to parse a generic
error message such that it can be embellished into html for use in the html
line, such that we can get color. There may be a requirement to rework the
generation of the drc error strings to facillitate easy parsing. Although
maybe we use structures instead of strings for error reporting so the parsing
does not need to happen.
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