15.03.2015 Views

SetupDesignGuide.pdf - Firmware Encoding Index

SetupDesignGuide.pdf - Firmware Encoding Index

SetupDesignGuide.pdf - Firmware Encoding Index

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Setup Design Guide<br />

DRAFT<br />

4.2.18 goto<br />

endpassword;<br />

minsize = 6,<br />

maxsize = 20,<br />

encoding = 1,<br />

This command allows the user to jump to a new page. In terms of HTML operations, this behaves<br />

exactly like a hyper-link. The target for a goto command is going to be a form.<br />

Example: goto formid PAGE_ONE,<br />

4.2.19 grayoutif<br />

prompt = STR_GOTO_PAGE_ONE;<br />

The grayoutif tag causes the following tag to be displayed in a special display form used for<br />

inaccessible options if the Boolean expression evaluates to true. Those writing IFR should realize that<br />

different browsers will support this option to varying degrees. In particular, HTML has no similar<br />

construct so may not support this facility.<br />

Example: grayoutif NvRamMap.MagicNumber == 3;<br />

4.2.20 suppressif<br />

The suppressif tag causes the following tag to be hidden from the user if the Boolean expression<br />

evaluates to true. As with grayoutif, the quality of support may vary from browser to browser.<br />

HTML does not itself have a mechanism to provide this functionality.<br />

Example: suppressif NvRamMap.SerialPortCount == 0;<br />

4.2.21 hidden<br />

Hidden input allows for communication of things like revision data between the creator of the VFR and<br />

the consumer. The user should not generally see hidden tags. Hidden tags can be used inside VFR<br />

along with the grayoutif and suppressif tags to control display of optional data.<br />

Example: hidden<br />

4.2.22 inconsistentif<br />

varid = NULL.CurrentIfrVersion,<br />

value = 2;<br />

This tag uses a Boolean expression to allow the creator of the IFR to check options in a richer manner<br />

than provided by the question tags themselves. This tag may be used to e.g. validate that two options<br />

aren’t using the same address or that numbers entered align to some pattern (like leap years and<br />

February in date input). The tag provides a string to be used in a “pop-up” display to alert the user to<br />

the issue. Inconsistency tags may be evaluated when the user traverses from tag to tag or only upon<br />

submission. The user should not be allowed to submit the results of a form inconsistencies.<br />

Example: inconsistentif<br />

endif;<br />

prompt = STR_ERROR_POPUP,<br />

ideqval NvRamMap.TestValue == 2,<br />

36

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!