Note: Displays a note dialog with text and a noti?¬?cation icon that indicates
information, error, or con?¬?rmation. Later, Note was extended to allow writing
custom code in the model element. In addition to writing plain code, reusing
functions written in Python was also supported. For this purpose, the Note
concept had an optional Function property type that referred to a Function in
the Function library. The available functions could thus be imported as code
?¬?les and refered to in models.
. Query: Displays a query dialog with a single ?¬?eld. In the language, this concept
had a property Prompt to enter the query label and Type to choose what kind of
value the query expects. This latter property was implemented as a list of ?¬?xed
values to be chosen from: ???text,??? ???code,??? ???number,??? ???date,??? ???time,??? or
???boolean???. The query dialog can include an optional initial value and the value
entered is stored as an optional, but unique, return variable. If a return variable
is not given, the value is treated as a local variable. This structure was also used
in other concepts, allowing values to be de?¬?ned that are used globally inside the
program. All queries return None if the user cancels the dialog. Further details
on navigation will be discussed later.
. Multiquery: A two-?¬?eld text input dialog.
Pages:
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313