and therefore tracks are now dragged when a end point is inside a pad, not necessary on the pad position.
However, drag functions still need more cleanup.
* Correct all user strings and comments for the correct capitalization of
application names according to JP. They are KiCad, Pcbnew, CvPcb,
Eeschema, and GerbView.
* Add a note the the user interface policy about the correct capitalization.
* All header files used to create the PCB common library now compile as
stand alone code. This prevents the need to define them in a specific
order to make source code compile properly. It should also now be
possible to relocate the source code to build the common PCB library
to a separate folder.
* in variable names, change non existent word Hight to High
* Remove redundant tool in left toolbar (option toolbar)
(this option is now in layers manager)
* Show layers in horizontal combo box in same order as in layer manager.
++all:
minor code cleaning.
* Moved ReturnLayerName() to static BOARD::GetDefaultLayerName() and migrated
to a Specctra DSN compatible default layer naming scheme:
Component becomes Front, Copper becomes Back.
* set_color.h: Cmp becomes Front, Cu becomes Back.
* D_PAD::DisplayInfo() changed to use actual copper layer names.
* more layer setup dialog work, moved all programmatic wxControl instantiation
into the wxFormbuilder environment, but this is fraught with danger:
wxFlexGridSizer used the tallest control to establish the row heights, so
be careful about changing control borders in the scroll panel. The vertical
size can explode since just a couple of pixels times the number of rows
is substantial. Currently I am setting a 5 pixel border only left, top, and right
but not bottom.
* Set copper layer count is back in place as a hack until I can get the enabled
layer bit map fully operational.
Small change in doc files: footprint_doc moved from help to share/modules
TODO: change dialog_cvpcb_config and copy code (from pcbnew) for multiple user paths in library path list in cvpcb.
pads option.) Haven't fixed the via issue
(since I don't quite understand why it is doing this, nor does it occur in 100% of the cases), but now you can just
turn
off magnetic tracks when I desire to move vias by small increments. Magnetic tracks are on by default. Original
via complaint here:
http://tech.groups.yahoo.com/group/kicad-devel/message/1155
Also mostly gotten rid of the annoying "Unable to drag this segment: two collinear segments" error. Now, if two
(or more) segments are collinear, they are merged into one equivalent segment when you try to drag them while
maintaining slope. I can't imagine any cases where this would be a bad thing (and I have plenty of experience where
the error was not desired!). Note I say *mostly* because there still seem to be some length=1 (e.g. 0.003mm) segments
at the end of valid-length segments. I do not want to remove them because this would change the board layout, though
in a basically imperceptible way. We could maybe have an option to clean & remove these minimal-length segments, but
I worry that they serve to connect things slightly off grid & those things on-grid; also, removal may cause DRC
errors. It would be good if we could avoid their creation.(?)
================================================================================
+eeschema
* commiting my changes to allow multiple instances of a given schematic file within
a hierarchy:
** internally, m_currentScreen has been replaced with m_currentSheet,
which is a list or 'path' of screens. The path of screens is used to
generate
a series of timestamps, which is converted to flat component reference via
a look-up
table in the schematic files.
** this means that m_currentScreen is no longer used -- use GetScreen().
** GetScreen is virtual, as some of the dialogs keep around a WinEDA_BaseScreen
pointer.
** all sub-sheets in a given schematic must have different names to generate a
meaningful netlist.
Lorenzo Marcantonio
jean-pierre charras
Dick Hollenbeck
Wayne Stambaugh
charras