1. 15 Jul, 2010 2 commits
  2. 14 Jul, 2010 3 commits
  3. 13 Jul, 2010 5 commits
  4. 12 Jul, 2010 4 commits
    • jean-pierre charras's avatar
      642d1f2e
    • Dick Hollenbeck's avatar
    • Dick Hollenbeck's avatar
      A little useful feature: even if the default unit can be changed between · d16bc738
      Dick Hollenbeck authored
      inches and mm, the industry is crazy enough to force us with mixed
      design. For example I routinely use imperial units for track size and
      clearance, but drilling is strictly a metric issue...
      
      So I added a little parser to recognize a suffix specification in the
      unit text boxes... so you can put in things like:
      1in (1 inch)
      1" (idem)
      25th (25 thou)
      25mi (25 mils, the same)
      6mm (6 mm, obviously)
      
      The rules are: spaces between the number and the unit are accepted, only
      the first two letters are significant.
      
      As a bonus, it also recognize the period (.) as a decimal point
      substituting it with the correct locale character (there was a wishlist
      for it, IIRC). Most useful for number pad fans :D
      d16bc738
    • Dick Hollenbeck's avatar
      A little useful feature: even if the default unit can be changed between · bc14e66d
      Dick Hollenbeck authored
      inches and mm, the industry is crazy enough to force us with mixed
      design. For example I routinely use imperial units for track size and
      clearance, but drilling is strictly a metric issue...
      
      So I added a little parser to recognize a suffix specification in the
      unit text boxes... so you can put in things like:
      1in (1 inch)
      1" (idem)
      25th (25 thou)
      25mi (25 mils, the same)
      6mm (6 mm, obviously)
      
      The rules are: spaces between the number and the unit are accepted, only
      the first two letters are significant.
      
      As a bonus, it also recognize the period (.) as a decimal point
      substituting it with the correct locale character (there was a wishlist
      for it, IIRC). Most useful for number pad fans :D 
      bc14e66d
  5. 11 Jul, 2010 3 commits
  6. 30 Jun, 2010 4 commits
  7. 28 Jun, 2010 2 commits
  8. 25 Jun, 2010 1 commit
  9. 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
  10. 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
  11. 21 Jun, 2010 2 commits
  12. 20 Jun, 2010 2 commits
  13. 19 Jun, 2010 2 commits
  14. 18 Jun, 2010 2 commits
  15. 17 Jun, 2010 3 commits
  16. 16 Jun, 2010 2 commits