Design Forms

It would not be a bad idea to agree on having a ceratin list of general E/W/N messages which would be then used among all the templates. The main purpose would be to avoid having several message for one issue.. As already discussed in the xml file would be the main set of E/W/N and then also some additional sets for example per check.. The most important would be to gether the general messages among the templates to have something to start with.. What do you think?

Jirka

EWN Codes MUST start with letter "E" (Errors), "W" (Warnings) or "N" (Notes).
The rest of the code is arbitrary.

I propose to share common EWN file on SVN.
I have prepared file urlhttps://svn.praha.scia.cz/rep_esa_61/contractors/OpenChecks/DesignForms%20P/_PublicDocuments/EWN/EWN_SCIA.xml/url
Each SDF developer can create his/her own messages to the local copy of that file. Than merge changes back to SVN.
To avoid EWN Code collisions, codes should be composed like this: i<E/W/N>_<DeveloperShortCut>_<Number>/i

uExamples:/u
E_VAL_01, W_DLO_05, N_POR_33.

size=150Inline strings/size
Version: 13.400.27+

EWN messages can now contain "place holders". These place holders are substituted with proper content at runtime.
Replacing content is defined by additional parameter of EWN.TraceEWN / EWN.TraceRectEWN command.

buExample of EWN messages with place holders:/u/b
W1 | Length of {0} edge is insufficient. | Increase length of {0} edge.

buExample of command with additional parameter:/u/b
EWN.TraceRectEWN("W1", 300, "S_Upper");

iSee attached example for more details.
Don't forget upload EWN_Example.xml to PublicDocuments\DesignForms_X.Y\EWN./i