Overview
The mvDesigner API included with FlashCONNECT enables FlashBASIC programs to work efficiently and effectively with mvDesigner applications. The mvDesigner API enables FlashCONNECT to drive mvDesigner applications or for the mvDesigner applications to use FlashCONNECT business rules.
Requirements
The following system requirements are needed to use the FlashCONNECT mvDesigner API:
FlashCONNECT installed on a D3 database server.
A development version of mvDesigner.
Design Goals
mvDesigner is designed so that a FlashCONNECT programmer can easily understand and use mvDesigner and the Omnis/mvDesigner developer to use mvDesigner business rules. mvDesigner enables FlashBASIC programmers to quickly create or convert FlashBASIC programs using the rich visual objects provided by mvDesigner GUI development tools.
Documentation Overview
mvDesigner consists of an API that enables the FlashCONNECT programmer to:
Retrieve information sent by the mvDesigner application.
Send data to the mvDesigner application.
Change the form displayed by the mvDesigner application.
Pop-up a message box.
Write persistent and non-persistent applications.
Pop-up multiple windows.
Show a progress bar for long running processes.
The mvDesigner API is used to send information to the mvDesigner application, while the standard FlashCONNECT API (such as w3GetVal, w3GetValAll) is used to retrieve information submitted by the mvDesigner application.
Typical Usage
include www w3include
Inserted once, usually toward the beginning of the program.
w3GetVal
Used as needed to retrieve information sent from the mvDesigner application.
w3mvDInit
Called once per form to optionally specify the next mvDesigner form to display. It is also called if the new form replaces or is layered on top of the current form and if the current top form should be closed.
w3mvDInsert
Used as needed to prepare data for transmission to the mvDesigner form.
w3mvDInput
Used once per form to send the data to the mvDesigner form and optionally wait for a reply.