The Evolution of MCL-Designer (from V3 to V4)

Navigation:  Getting Started with MCL-Designer V4 >

The Evolution of MCL-Designer (from V3 to V4)

Previous pageReturn to chapter overviewNext page

 

Overview

 

This chapter focuses on a direct feature comparison between the previous MCL-Designer V3 and MCL-Designer V4. This is directly beneficial to those already familiar with the MCL-Collection.

 

 


MCL-Designer V3

MCL-Designer V4

Unicode Support.

Web Services Client Integration (http).

Peripheral Support (phone, camera, GPS, RFID, etc.).

Local Database Support on Client.

Multiple Monitor Setup.

Support to high resolution monitors

Code Execution.

Sequential execution

 

The project is created following a rigid structure:

Creating a main program ➔ adding a screen ➔ adding controls to a screen ➔ adding processes [process in/process out]) ➔ adding a screen ➔ automatically continues (sequence).

Action driven execution

 

The creation of a project is NOT linear, but flexible. Now, the next action/control/process must be called in order to continue the workflow (trigger).

 

Sequential execution emulation

 

The use of the “routine in” (runs before the screen is mapped) and/or the “routine out” (runs after all the controls of the screen have been validated) within a project emulates a sequential execution.

 

Templates.

 

Focus on using predefined templates instead of creating custom ones.

Example:

 

Processes when entering a Screen.

“Process – In”

“Routine In”

 

Used to perform some actions prior to painting controls on a screen.

Processes when leaving a Screen.

“Process – Out”

“Validate”

 

Use this action when all controls on the screen have been validated according to the rules specified within the control.

 

"Routine Out" (Legacy)

 

Used to perform actions after all the controls of the screen have been validated.

Procedures with Input/Output arguments (Global and Local Procedures).

Reusability of functions, controls and code

 

(Design function once, use across multiple client/server). This allows for Cross Developer maintenance.

A set of instructions to perform recurrent or shared functions locally (inside a program). Similar to a local procedure.

Its start and finish is marked with a label and an explicit “Go to Exit”.

Subroutine

Routine

Multiple Language Support.

Possibility to dynamically change the language used in your project.

GUI theme selection for the project.

Input Control’s new features.

 

Hint ( shadowed text inside the control).

SIP (calls a virtual keyboard).

 

 

Screen Control Properties.

 

Alignment

Tab Stop

Send to Front/Back

Visible/Not Visible

Enabled/Disabled

Auto Refresh

See Setting Screen Properties

 

 

“Drag and Drop” of images from the OS File Explorer directly into the Resources section.

Enhanced graphic feature that automatically resizes all visual control without rescaling.