|
|
| Line 1: |
Line 1: |
| − | __NOINDEX__
| |
| | | | |
| − | TODO
| |
| − |
| |
| − | <big>'''Dropdowns - Reliability & Usability'''</big><br />
| |
| − | - Show all different types of choices and when they're applicable
| |
| − |
| |
| − | <big>'''Choice Dropdowns'''</big><br />
| |
| − | One of the biggest missed opportunities we see at Lumina when reviewing customer & client models is the infrequent use of the Choice() and MultiChoice() functions. Making use of these will not only make your model more clear from a client perspective, but will also make your model more flexible should something like an index change in the future.
| |
| − |
| |
| − | To demonstrate this you can view the video below or read on:
| |
| − | '''VIDEO EMBED HERE'''
| |
| − |
| |
| − | <big>'''Choices as Labels'''</big><br />
| |
| − | When trying to make our model more flexible we should think of using Choice() as a "label". A label as we describe it is a node that uses Choice() to reference a value from an index. The value of this should become more apparent from the following example.
| |
| − |
| |
| − | ''Scenario''
| |
| − | I've created a model that references values in my index called "Fruits". However, I notice midway through development that I've actually made a typo in my index:
| |
| − | [[File:Choice_Tips_1.jpg]]<br />
| |
| − |
| |
| − | If I fix the typo in my index then '''everywhere else I reference it in the model will break'''. This headache could've been easily avoided by making use of labels. Here's how that could look:
| |
| − | [[File:Choice_Tips_2.jpg]]<br />
| |
| − |
| |
| − | Labels take care of issues like typos because they all references point to a single label node that grabs its value based on the position in an index.
| |
| − |
| |
| − | To use labels, find the parts of the model that reference an element from the index and then instead of typing something like <br />[Fruits = 'Apples']<br />
| |
| − |
| |
| − | you would type
| |
| − | <br />[Fruits = Apples_Label]<br />
| |
| − |
| |
| − |
| |
| − | Another reason this is to help track where specific elements of an index are being used. If there was a different reason why I wanted to find every place 'Apples' was used in my model, I could look at the object window for Apples_Label and view the list of Outputs:
| |
| − | [[File:Choice_Tips_3.jpg]]<br />
| |
Enable comment auto-refresher