1. 11 Jul, 2010 1 commit
  2. 30 Jun, 2010 4 commits
  3. 28 Jun, 2010 2 commits
  4. 25 Jun, 2010 1 commit
  5. 24 Jun, 2010 1 commit
    • Wayne Stambaugh's avatar
      EESchema component library and hierarchical sheet label object improvements. · e1b5d49f
      Wayne Stambaugh authored
      * Continue component library class clean up and encapsulation work.
      * Change hierarchical sheet label container to boost::vector_ptr.
      * Encapsulate hierarchical label handling in hierarchical sheet class.
      * Convert some missed occurrences of wxString::GetData() to GetChars( wxString ).
      * Fix some minor code formatting issues.
      e1b5d49f
  6. 23 Jun, 2010 2 commits
    • jean-pierre charras's avatar
      ++eeschema: · bf9e49dd
      jean-pierre charras authored
          In netlist generation, changed the rule to calculate netnames of nets with labels:
          Previously, named nets (i.e. nets with local, hierarchical or global labels) have their name
          defined by the first label found in list.
          So net names could be changed without really changing the schematic.
          Now the names are calculated from the rules (by priority order) :
          1 - use the most top level labels in hierarchies.
          2 - use global labels first, local labels next (hidden power pins names are global labels).
          3 - use alphabetic sort (so, if GND and AGND are connected, the net will be always named AGND,
          and adding a VSS connection cannot change the net name)
          So power nets and nets that have more than one label cannot have their netname changed
          if there is no actual change relative to these nets names in schematic
      bf9e49dd
    • jean-pierre charras's avatar
      ++eeschema: · 3543ba65
      jean-pierre charras authored
          In netlist generation, changed the rule to calculate netnames of nets with labels:
          Previously, named nets (i.e. nets with local, hierarchical or global labels) have their name
          defined by the first label found in list.
          So net names could be changed without really changing the schematic.
          Now the names are calculated from the rules (by priority order) :
          1 - use the most top level labels in hierarchies.
          2 - use global labels first, local labels next (hidden power pins names are global labels).
          3 - use alphabetic sort (so, if GND and AGND are connected, the net will be always named AGND,
          and adding a VSS connection cannot change the net name)
          So power nets and nets that have more than one label cannot have their netname changed
          if there is no actual change relative to these nets names in schematic
      3543ba65
  7. 21 Jun, 2010 2 commits
  8. 20 Jun, 2010 2 commits
  9. 19 Jun, 2010 2 commits
  10. 18 Jun, 2010 2 commits
  11. 17 Jun, 2010 3 commits
  12. 16 Jun, 2010 2 commits
  13. 15 Jun, 2010 5 commits
  14. 14 Jun, 2010 2 commits
  15. 13 Jun, 2010 1 commit
  16. 12 Jun, 2010 2 commits
  17. 11 Jun, 2010 1 commit
  18. 10 Jun, 2010 3 commits
  19. 08 Jun, 2010 1 commit
  20. 06 Jun, 2010 1 commit