| 209 | | # self.Keys does not have the requested key. This could happen, for |
|---|
| 210 | | # example, if the bound field is a foreign key, and we are just adding |
|---|
| 211 | | # a new record. In my case, the iclientid field is ''. I want the list |
|---|
| 212 | | # to display "< None >" and map that to a value of None, so I set up a |
|---|
| 213 | | # Choice and a Key for that in my app code. |
|---|
| 214 | | |
|---|
| 215 | | # setting key to None here will result in an exception if there is no |
|---|
| 216 | | # key on None (user code must set their Keys to have a None key). But |
|---|
| 217 | | # the effect this has is that if the control is getting set to a value |
|---|
| 218 | | # that doesn't exist in self.Keys, we'll set the list to select the |
|---|
| 219 | | # item that is matched to None, if available. Else, it's a runtime |
|---|
| 220 | | # exception. |
|---|
| | 209 | # If the appdev set up a key for None, use it. |
|---|