Change data representation on the Front Panel in CLD exam

[AuZn]

I understand that front panel is provided in the CLD exam. Can I change the data representation if I think it is necessary/more convinient for my purpose? e.g. change i32 into u32 or double...

[Fisel · Accepted solution]

Short answer, no.  The scenario/perspective is you developing an application according to someone else's specs.

[AuZn]

Thanks. Then I suppose changing mechanical behavior of a bottun is not allowed either?

[Fisel]

Correct, by same logic.

[JÞB]

---

@AuZn wrote:

I understand that front panel is provided in the CLD exam. Can I change the data representation if I think it is necessary/more convinient for my purpose? e.g. change i32 into u32 or double...

---

I'll amplify a bit on the absolutely correct advice Fisel supplied.  Do Not mess with any supplied FP object properties except Description & Tip (DO Add them!) and, of course, Value.  Its pointless to have a FP object whos value does not change right?

Now, IF you do find an idea where a supplied FP object's property is less desireable than you want (very possilbe and a common real-world problem) Comment it!  Something like "#Clarify with client. A change of property X would be advantagous for <Reason>"  Thats just good client communication!  Not a bad skill for a CLD to have.

[AuZn]

Just thought of another issue: can I make typedefs of provided front panel objects? Also no?

[JÞB]

Also "Yes" but comment why.  

As a general rule "Do not mess with provided FP Objects except documentation- unless you comment WHY you messed with them or would prefer to mess with them"

And, if you do type def a control / indicator, Flipping change the default icon!  Yes, that is a pet peeve of mine, default icons for type-def controls! Damn, I've seen 10+ year CLAs screw that up!  and "View>>Browse Relationships>>Unopened Type Defs.  becomes a quagmire.