![]() Note that when you define screen flow, triggers, and actions which we will describe in the following paragraphs, you are not only enabling the execution of your UI from within the Studio environment, but you are also enabling GUIX Studio to generate logic within your specifications file that will handle events and take actions based on those events, such as transitioning from one screen to another. These effects and animations can be observed directly from within the GUIX Studio environment. ![]() Still, this capability allows you to auto-generate screen transition logic, and program animations to be executed to transition from one screen to another. Custom drawing functions, custom event handlers, and complex event handling are not available when running the application from within the GUIX Studio environment. There are of course limitations to what can be done without compiling the application. Running the application on your desktop from within the Studio environment is a handy feature which saves time in that you are not required to go through a compile/link cycle to execute your application. When a screen flow diagram is added to the project, it enables two important features: 1) The application can be executed from within the Studio environment and 2) Studio automatically generates event handlers and screen transition logic to implement the designated screen flow within the generated specifications.c file, removing this burden from the application program. The user defines the screen transition logic by creating and editing a graphical screen flow diagram. GUIX Studio supports automatic generation and execution of screen transition logic.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |