Trace: • Formatting Cells in Tables • Formatting Tree Nodes
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
jvx:client:gui:screen_parameters [2021/07/08 10:47] admin |
jvx:client:gui:screen_parameters [2021/07/08 10:48] (current) admin |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| <code java> | <code java> | ||
| //construction time | //construction time | ||
| - | IWorkScreen screen = getApplication().openWorkscreen("com.apps.demo.ContactWorkScreen", new Parameter("CONTACT_ID", rdb.getValue("ID"))); | + | IWorkScreen screen = getApplication().openWorkScreen("com.apps.demo.ContactWorkScreen", new Parameter("CONTACT_ID", rdb.getValue("ID"))); |
| //later | //later | ||
| Line 41: | Line 41: | ||
| screen.getParameter("APPMODE") | screen.getParameter("APPMODE") | ||
| </code> | </code> | ||
| - | and the parameter was not found in the work-screen, then the parameter will be requested from the application. The application also has getParameter. If the parameter is not set in the application, the launcher will be used. This mechanism makes it possible for a screen to configure itself based on launcher, application or a screen parameter. For the screen it makes no difference where the parameter was set. But be careful because the event listeners only work if you register on the right component. It's not possible to register a listener for a parameter of a screen and expect a change event, if you set the parameter in the application. | + | and the parameter was not found in the work-screen, then the parameter will be requested from the application. The application also has getParameter. If the parameter is not set in the application, the [[jvx:client:gui:application_parameters|launcher]] will be used. This mechanism makes it possible for a screen to configure itself based on launcher, application or a screen parameter. For the screen it makes no difference where the parameter was set. But be careful because the event listeners only work if you register on the right component. It's not possible to register a listener for a parameter of a screen and expect a change event, if you set the parameter in the application. |