Changes

Some generic Formatting guides - consistent with how classes are usually written.

Use protected as a heading for a number of declarations.
I believe that the previous formatting in Digitial is due to someone having
protected A
protected B
protected C
(which would be another style).
Then the subsequent protected were lost, and first protected formatted on a separate line.

Avoid bad line-breaks in connect-annotation.

Do not use tab.
(Additional changes would be good.)

Remove trailing white-space

The end of a class shall not be indented relative to class.

RemoveTrailingWhiteSpace

NoTab

Even for redeclare extends ensure that class contents is indented relative to class.

Indent annotation relative to class

Documentation shall be indented relative to class

And sensible formatting

Use protected as heading consistently.

Remove weird line-breaks and format equation consistently.

Add separation rule as well.

And apply the rule

Update Modelica/Electrical/Machines/Sensors/CurrentQuasiRMSSensor.mo

Apply suggestions from code review

Co-authored-by: Henrik Tidefelt <henrikt@wolfram.com>

Apply suggestions from code review

Minor formatting changes in html code

Apply suggestions from code review

Co-authored-by: tobolar <tobolar@users.noreply.github.com>

Specify how to handle modifier lists.
Give example.

Rename to be slightly better.

Quoting!

Type Modelica keywords in bold and remove trailing whitespaces ;-)

Based on comments in #4156 just remove eps.

Some generic Formatting guides - consistent with how classes are usually written.

Use protected as a heading for a number of declarations.
I believe that the previous formatting in Digitial is due to someone having
protected A
protected B
protected C
(which would be another style).
Then the subsequent protected were lost, and first protected formatted on a separate line.

Avoid bad line-breaks in connect-annotation.

Do not use tab.
(Additional changes would be good.)

Remove trailing white-space

The end of a class shall not be indented relative to class.

RemoveTrailingWhiteSpace

NoTab

Even for redeclare extends ensure that class contents is indented relative to class.

Indent annotation relative to class

Documentation shall be indented relative to class

And sensible formatting

Use protected as heading consistently.

Remove weird line-breaks and format equation consistently.

Add separation rule as well.

And apply the rule

Update Modelica/Electrical/Machines/Sensors/CurrentQuasiRMSSensor.mo

Apply suggestions from code review

Co-authored-by: Henrik Tidefelt <henrikt@wolfram.com>

Apply suggestions from code review

Minor formatting changes in html code

Apply suggestions from code review

Co-authored-by: tobolar <tobolar@users.noreply.github.com>

Specify how to handle modifier lists.
Give example.

Rename to be slightly better.

Quoting!

Type Modelica keywords in bold and remove trailing whitespaces ;-)

Based on comments in #4156 just remove eps.

Some generic Formatting guides - consistent with how classes are usually written.

Use protected as a heading for a number of declarations.
I believe that the previous formatting in Digitial is due to someone having
protected A
protected B
protected C
(which would be another style).
Then the subsequent protected were lost, and first protected formatted on a separate line.

Avoid bad line-breaks in connect-annotation.

Do not use tab.
(Additional changes would be good.)

Remove trailing white-space

The end of a class shall not be indented relative to class.

RemoveTrailingWhiteSpace

NoTab

Even for redeclare extends ensure that class contents is indented relative to class.

Indent annotation relative to class

Documentation shall be indented relative to class

And sensible formatting

Use protected as heading consistently.

Remove weird line-breaks and format equation consistently.

Add separation rule as well.

And apply the rule

Update Modelica/Electrical/Machines/Sensors/CurrentQuasiRMSSensor.mo

Apply suggestions from code review

Co-authored-by: Henrik Tidefelt <henrikt@wolfram.com>

Apply suggestions from code review

Minor formatting changes in html code

Apply suggestions from code review

Co-authored-by: tobolar <tobolar@users.noreply.github.com>

Specify how to handle modifier lists.
Give example.

Rename to be slightly better.

Quoting!

Type Modelica keywords in bold and remove trailing whitespaces ;-)

Based on comments in #4156 just remove eps.

Some generic Formatting guides - consistent with how classes are usually written.

Use protected as a heading for a number of declarations.
I believe that the previous formatting in Digitial is due to someone having
protected A
protected B
protected C
(which would be another style).
Then the subsequent protected were lost, and first protected formatted on a separate line.

Avoid bad line-breaks in connect-annotation.

Do not use tab.
(Additional changes would be good.)

Remove trailing white-space

The end of a class shall not be indented relative to class.

RemoveTrailingWhiteSpace

NoTab

Even for redeclare extends ensure that class contents is indented relative to class.

Indent annotation relative to class

Documentation shall be indented relative to class

And sensible formatting

Use protected as heading consistently.

Remove weird line-breaks and format equation consistently.

Add separation rule as well.

And apply the rule

Update Modelica/Electrical/Machines/Sensors/CurrentQuasiRMSSensor.mo

Apply suggestions from code review

Co-authored-by: Henrik Tidefelt <henrikt@wolfram.com>

Apply suggestions from code review

Minor formatting changes in html code

Apply suggestions from code review

Co-authored-by: tobolar <tobolar@users.noreply.github.com>

Specify how to handle modifier lists.
Give example.

Rename to be slightly better.

Quoting!

Type Modelica keywords in bold and remove trailing whitespaces ;-)

Based on comments in #4156 just remove eps.

Some generic Formatting guides - consistent with how classes are usually written.

Use protected as a heading for a number of declarations.
I believe that the previous formatting in Digitial is due to someone having
protected A
protected B
protected C
(which would be another style).
Then the subsequent protected were lost, and first protected formatted on a separate line.

Avoid bad line-breaks in connect-annotation.

Do not use tab.
(Additional changes would be good.)

Remove trailing white-space

The end of a class shall not be indented relative to class.

RemoveTrailingWhiteSpace

NoTab

Even for redeclare extends ensure that class contents is indented relative to class.

Indent annotation relative to class

Documentation shall be indented relative to class

And sensible formatting

Use protected as heading consistently.

Remove weird line-breaks and format equation consistently.

Add separation rule as well.

And apply the rule

Update Modelica/Electrical/Machines/Sensors/CurrentQuasiRMSSensor.mo

Apply suggestions from code review

Co-authored-by: Henrik Tidefelt <henrikt@wolfram.com>

Apply suggestions from code review

Minor formatting changes in html code

Apply suggestions from code review

Co-authored-by: tobolar <tobolar@users.noreply.github.com>

Specify how to handle modifier lists.
Give example.

Rename to be slightly better.

Quoting!

Type Modelica keywords in bold and remove trailing whitespaces ;-)

Based on comments in #4156 just remove eps.

Some generic Formatting guides - consistent with how classes are usually written.

Use protected as a heading for a number of declarations.
I believe that the previous formatting in Digitial is due to someone having
protected A
protected B
protected C
(which would be another style).
Then the subsequent protected were lost, and first protected formatted on a separate line.

Avoid bad line-breaks in connect-annotation.

Do not use tab.
(Additional changes would be good.)

Remove trailing white-space

The end of a class shall not be indented relative to class.

RemoveTrailingWhiteSpace

NoTab

Even for redeclare extends ensure that class contents is indented relative to class.

Indent annotation relative to class

Documentation shall be indented relative to class

And sensible formatting

Use protected as heading consistently.

Remove weird line-breaks and format equation consistently.

Add separation rule as well.

And apply the rule

Update Modelica/Electrical/Machines/Sensors/CurrentQuasiRMSSensor.mo

Apply suggestions from code review

Co-authored-by: Henrik Tidefelt <henrikt@wolfram.com>

Apply suggestions from code review

Minor formatting changes in html code

Apply suggestions from code review

Co-authored-by: tobolar <tobolar@users.noreply.github.com>

Specify how to handle modifier lists.
Give example.

Rename to be slightly better.

Quoting!

Type Modelica keywords in bold and remove trailing whitespaces ;-)

Based on comments in #4156 just remove eps.

Some generic Formatting guides - consistent with how classes are usually written.

Use protected as a heading for a number of declarations.
I believe that the previous formatting in Digitial is due to someone having
protected A
protected B
protected C
(which would be another style).
Then the subsequent protected were lost, and first protected formatted on a separate line.

Avoid bad line-breaks in connect-annotation.

Do not use tab.
(Additional changes would be good.)

Remove trailing white-space

The end of a class shall not be indented relative to class.

RemoveTrailingWhiteSpace

NoTab

Even for redeclare extends ensure that class contents is indented relative to class.

Indent annotation relative to class

Documentation shall be indented relative to class

And sensible formatting

Use protected as heading consistently.

Remove weird line-breaks and format equation consistently.

Add separation rule as well.

And apply the rule

Update Modelica/Electrical/Machines/Sensors/CurrentQuasiRMSSensor.mo

Apply suggestions from code review

Co-authored-by: Henrik Tidefelt <henrikt@wolfram.com>

Apply suggestions from code review

Minor formatting changes in html code

Apply suggestions from code review

Co-authored-by: tobolar <tobolar@users.noreply.github.com>

Specify how to handle modifier lists.
Give example.

Rename to be slightly better.

Quoting!

Type Modelica keywords in bold and remove trailing whitespaces ;-)

Based on comments in #4156 just remove eps.