Calcpad version 5.8.2

[Proektsoftbg]

Fixed breach of *.cpdz files by saving as *.cpd. See #28 (comment)

Counting of input fields in the source code is now correct.

Added C-style relational operators: ==, !=, >=, <= as per #38, No 4. They work as shortcuts to the respective Calcpad operators and are replaced after leaving the current line, as follows:
== => ≡
!= => ≠
>= => ≥
<= => ≤

Fixed resetting input fields to zero after editing the source code.

Fixed resetting input fields to zero after undo all steps.

The replacement of Html select input with text in the output is performed only if class "post" is added to the select element.

Fixed macro replace order bug, issue #40.

Images are inserted on the current line (not in the beginning of the document), issue #36.

---

This discussion was created from the release Calcpad version 5.8.2.

[idealkindom]

Nice to install 5.8.2.I have found 2 problems. 1 is the display of operator of sqrt is not normal, it looks like a number capped. 2 is when I run the self contained example cpd of "cubic equation", it errors strangely. Concerning this I suggest that when the angle system is degree, the superscript should be added mandatorily, otherwise it should be reckoned as rad.

[Proektsoftbg]

1. Can you please share a screenshot? It looks OK for me:

3. After angle units were introcuced, some worksheets need to be updated. acos on line 14 returns the value of θ in radians. So, we also have to make 2*π also in radians.

[idealkindom]

Another problem is when you plot multiple function,Calcpad use varied colors to make them apart, but can we add linetype and symbols and legend to make it more manifest to show.

[idealkindom]

Ned U are right, its due to ie 11 on Windows 7.Anyway the output html, word and pdf are normal.

[idealkindom]

the output html still display sqrt abnormally, but supported well in other web browsers.

[Proektsoftbg]

Another problem is when you plot multiple function,Calcpad use varied colors to make them apart, but can we add linetype and symbols and legend to make it more manifest to show.

@idealkindom Yes, this is what we have not developed yet. A fully featured customizable charting (line in Excel) is a tedious job to implement, but it is possible to do it in future. Currently, you can add your own legend in a very simple and easy way with a little Html. You can check this example:

https://calcpad.eu/Worksheet/20/column-design-for-bending-and-axial-force

...and the source code:

https://github.com/Proektsoftbg/Calcpad/blob/main/Examples/Structural%20Design/Reinforced%20Concrete/Column%20Design%20for%20Bending%20and%20Axial%20Force.cpd

The legend is generated by the following code:

'<p><b>Legend:</b></p>
'<p><b style="color:Red">————</b> Interaction diagram</p>
'<p><b style="color:Green">————</b> Line of geometric imperfections</p>
'<p><b style="color:Blue">————</b> Buckling curve</p>
'<p><b style="color:Goldenrod">●</b> Design resistance including geometric imperfections and accidental eccentricity - <i>N</i><sub>Rd_ei</sub></p>
'<p><b style="color:Magenta">●</b> Design buckling resistance - <i>N</i><sub>Rd_II</sub></p>
'<p><b style="color:DarkCyan">●</b> Design load № 1, <b style="color:Purple">●</b> Design load № 2, <b style="color:DarkOrange">●</b> Design load № 3,</p>
'<p><b style="color:Maroon">●</b> Design load № 4, <b style="color:YellowGreen">●</b> Design load № 5</p>

These are the actual colors, used in the diagrams. You can use the above code as a boilerplate for your legends.

[idealkindom]

Thanks Ned.Since I generally use mobile phone to see github, I choose to send the screen shoot to your email.

for the problem 2, I think your correction rightly support my oponion.Because you see rad in fact is not a unit, because the dimension is 1. In the example you never input a rad for theta or some other parameter, it looks so strange to intensionally add a rad behind pi, which is in fact the ratio of circumference of a cirle to its diameter.For me it's a little wierd.I don't know what other users think about it.

[Proektsoftbg]

I can see what you mean. We did not enter radians for θ, but they are returned by the acos function. pi itself is just a number. You should add rad not to pi, but for the angle (the argument of the cos function). Angle units are dimensionless in physical point of view but they are still units. We must check for consistency. You have to make difference between dimensionless units and unitless values.

In future, we can add other dimensionless unitslike money (USD, EUR) or information (bit, byte, MB). They are also units like deg, rad and grad, but also not physical ones. It would be rather strange, if we could write 2USD + 20GB + 2rad. Thence, dimensionless units also have to be consistent.

So, rad is dimensionless, but it is a unit as well. We already realized hat without it, we do not have a consistent unit system for angles and cannot perform proper conversion and arithmetic operations. To illustrate why rad is not equal to 1, check the following example:

90°/2 ' = 45°
90°/2rad ' = 0.785

You see that 2 is not equal to 2rad. Otherwise, we would not know whether we want to divide the angle by two equal parts or calculate the relation to another angle with is in radians.

However, we have another option - to make θ unitless just after the acos function on line 14:

#hide
θ = θ/rad
#show

... and then continue in the old way.

What we probably need is an option whether inverse trigonometric functions should return a unitless value or in the default angle units. The later is needed, if you want to convert it or play with the units in some way later. Then, we can avoid updating the old worksheets, by setting the default behaviour to be the same like before. Changing the behaviour of so important functions can be very frustrating to sers.
Here I can agree with you completely.

[Proektsoftbg]

Nevertheless, I restored the default behaviour of inverse trigonometric functions to return just unitless numbers as before.
If you need to have the units attached, you will have to define a variable ReturnAngleUnits = 1 in the beginning. In this way, the old worksheets will not give errors and we will not need to amend them.

[idealkindom]

Nevertheless, I restored the default behaviour of inverse trigonometric functions to return just unitless numbers as before. If you need to have the units attached, you will have to define a variable ReturnAngleUnits = 1 in the beginning. In this way, the old worksheets will not give errors and we will not need to amend them.

Thanks Ned. I find it looks like the atuo completion would always cause 2 # like "##if".