7
mirror of https://gitlab.com/kicad/code/kicad.git synced 2025-04-21 00:21:25 +00:00

Fix some typos

This commit is contained in:
aris-kimi 2024-11-24 16:44:01 +00:00 committed by jean-pierre charras
parent 090500789e
commit e917e03a10
5 changed files with 12 additions and 6 deletions

View File

@ -237,7 +237,7 @@ public:
/**
* Slide the zoom steps over for debugging things "up close".
*
* Setting name: "EnableRouterDump"
* Setting name: "HyperZoom"
* Valid values: 0 or 1
* Default value: 0
*/
@ -422,7 +422,7 @@ public:
*
* This is used for calculating the bevel's height.
*
* Setting name: "V3DRT_BevelHeight_um"
* Setting name: "V3DRT_BevelExtentFactor"
* Valid values: 0 to 100
* Default value: 1/16
*/
@ -621,6 +621,9 @@ public:
/**
* Log IPC API requests and responses
*
* Setting name: "EnableAPILogging"
* Default value: false
*/
bool m_EnableAPILogging;
@ -697,6 +700,9 @@ public:
/**
* Minimum overlapping angle for which an arc is considered to be parallel
* to its paired arc.
*
* Setting name: "MinParallelAngle"
* Default value: 0.001
*/
double m_MinParallelAngle;

View File

@ -437,7 +437,7 @@ DIALOG_PAD_PROPERTIES_BASE::DIALOG_PAD_PROPERTIES_BASE( wxWindow* parent, wxWind
m_holeShapeLabel->Wrap( -1 );
m_gbSizerHole->Add( m_holeShapeLabel, wxGBPosition( 0, 0 ), wxGBSpan( 1, 1 ), wxALIGN_CENTER_VERTICAL|wxLEFT|wxRIGHT, 5 );
wxString m_holeShapeCtrlChoices[] = { _("Circular"), _("Oval") };
wxString m_holeShapeCtrlChoices[] = { _("Round"), _("Oblong") };
int m_holeShapeCtrlNChoices = sizeof( m_holeShapeCtrlChoices ) / sizeof( wxString );
m_holeShapeCtrl = new wxChoice( m_panelGeneral, wxID_ANY, wxDefaultPosition, wxDefaultSize, m_holeShapeCtrlNChoices, m_holeShapeCtrlChoices, 0 );
m_holeShapeCtrl->SetSelection( 1 );

View File

@ -5234,7 +5234,7 @@
<property name="caption"></property>
<property name="caption_visible">1</property>
<property name="center_pane">0</property>
<property name="choices">&quot;Circular&quot; &quot;Oval&quot;</property>
<property name="choices">&quot;Round&quot; &quot;Oblong&quot;</property>
<property name="close_button">1</property>
<property name="context_help"></property>
<property name="context_menu">1</property>

View File

@ -7,7 +7,7 @@ _HKI( "### Constraints\n"
"| `assertion` | \"&lt;expression>\" | Checks the given expression.<br> |\n"
"| `clearance` | min | Specifies the **electrical** clearance between copper objects of different nets. (See `physical_clearance` if you wish to specify clearance between objects regardless of net.)<br><br>To allow copper objects to overlap (collide), create a `clearance` constraint with the `min` value less than zero (for example, `-1`).<br> |\n"
"| `courtyard_clearance` | min | Checks the clearance between footprint courtyards and generates an error if any two courtyards are closer than the `min` distance. If a footprint does not have a courtyard shape, no errors will be generated from this constraint.<br> |\n"
"| `creepage` | min | Specifies the **electrical** creepage between copper objects of different nets.<br> |\n"
"| `creepage` | min | Specifies the creepage distance between copper objects of different nets.<br> |\n"
"| `diff_pair_gap` | min/opt/max | Checks the gap between coupled tracks in a differential pair. Coupled tracks are segments that are parallel to each other. Differential pair gap is not tested on uncoupled portions of a differential pair (for example, the fanout from a component).<br> |\n"
"| `diff_pair_uncoupled` | max | Checks the distance that a differential pair track is routed uncoupled from the other polarity track in the pair (for example, where the pair fans out from a component, or becomes uncoupled to pass around another object such as a via).<br> |\n"
"| `disallow` | `track`<br>`via`<br>`micro_via`<br>`buried_via`<br>`pad`<br>`zone`<br>`text`<br>`graphic`<br>`hole`<br>`footprint`<br> | Specify one or more object types to disallow, separated by spaces. For example, `(constraint disallow track)` or `(constraint disallow track via pad)`. If an object of this type matches the rule condition, a DRC error will be created.<br><br>This constraint is essentially the same as a keepout rule area, but can be used to create more specific keepout restrictions.<br> |\n"

View File

@ -6,7 +6,7 @@
| `assertion` | "&lt;expression>" | Checks the given expression.<br> |
| `clearance` | min | Specifies the **electrical** clearance between copper objects of different nets. (See `physical_clearance` if you wish to specify clearance between objects regardless of net.)<br><br>To allow copper objects to overlap (collide), create a `clearance` constraint with the `min` value less than zero (for example, `-1`).<br> |
| `courtyard_clearance` | min | Checks the clearance between footprint courtyards and generates an error if any two courtyards are closer than the `min` distance. If a footprint does not have a courtyard shape, no errors will be generated from this constraint.<br> |
| `creepage` | min | Specifies the **electrical** creepage between copper objects of different nets.<br> |
| `creepage` | min | Specifies the creepage distance between copper objects of different nets.<br> |
| `diff_pair_gap` | min/opt/max | Checks the gap between coupled tracks in a differential pair. Coupled tracks are segments that are parallel to each other. Differential pair gap is not tested on uncoupled portions of a differential pair (for example, the fanout from a component).<br> |
| `diff_pair_uncoupled` | max | Checks the distance that a differential pair track is routed uncoupled from the other polarity track in the pair (for example, where the pair fans out from a component, or becomes uncoupled to pass around another object such as a via).<br> |
| `disallow` | `track`<br>`via`<br>`micro_via`<br>`buried_via`<br>`pad`<br>`zone`<br>`text`<br>`graphic`<br>`hole`<br>`footprint`<br> | Specify one or more object types to disallow, separated by spaces. For example, `(constraint disallow track)` or `(constraint disallow track via pad)`. If an object of this type matches the rule condition, a DRC error will be created.<br><br>This constraint is essentially the same as a keepout rule area, but can be used to create more specific keepout restrictions.<br> |