Settings - Conversion rules
1. Use this name of global Zoom event in Main Program
For all Zoom events on controls, which are created during conversion process, use one global Zoom event. This setting allows you to specify the name of this event. 'gZoom' is default name.
2. Add "Next Field" event to Zoom After
Zoom After, in RM Compatible, is converted to Zoom event handler, with appropriate operation/s in handler. This setting specifies whether cursor moves to next field after Zoom After event is executed on control.
3. Add "Next Field" event to Zoom Before
Zoom Before, in RM Compatible, is converted to Zoom event handler, with appropriate operation/s in handler. This setting specifies whether cursor moves to next field after Zoom After event is executed on control.
4. Set Zoom Handler to be Propagate
Set Yes/No to specify how Zoom event handlers are created during conversion process.
5. Convert operations with Combine direction in Verification to: Forward / Backward / Both
Instruct conversion process how the operations with Flow direction = Combine are converted.
6. Convert Verify Error operations to: Verify Revert / Verify Error
In eDeveloper v10 Verify Error behaves differently than in previous versions of eDeveloper. In v10, Verify Error stops the engine flow and the flow doesn't execute all preceding operations backwards toward the Select. For this case, Verify Revert has been implemented. when Verify Revert is executed, after it shows the message, the flow returns through all the preceding operations and execute them.
This setting defines what is Verify Error converted into.
7. Apply Unique Control Name to controls with blank Control Name on Form
In event-driven mechanism, in order to execute Event attached to a control, it has to have a Control Name set. During conversion process all Controls that have events attached, have their Control Name set.
This setting will also determine whether all other Controls, which don't have any events attached to them, have Control Name set. this is good practice, in case in future this control will have any events attached.
8. Remove operations or Blocks with Condition = No or 'False'LOG
Conversion process can automatically remove any operations that are not executed.
9. Change Program's Last updated date
Indication whether the conversion process saves the date and time of conversion as Last update date for each program.
Group by Control Name
Sort handlers around each Control Name.
Group Events together
Sort handlers in a way to group Event handlers together at the end.
Remove all empty handlers. Conversion from eDeveloper v9 into v10 could have created empty handlers, such as Task Prefix/Suffix and Record Prefix/Suffix. During conversion with RM Converter you can choose whether ALL empty handlers are removed.
12. If Form is empty, convert all operations to: Task Prefix / New Logic unit / Ignore
In cases where there are no variables on Forms, or Form is completely empty, all of the operations will be executed in one flow. These can be converted either to Task Prefix, New Logic unit or can be Ignored.
When New Logic unit is created with all of the operations, the Logic unit is not connected to any of the controls. It is up to developer to decide how to handle these situations.
NOTE: All settings are saved as you set them. So, next time RM Converter is run, all the settings will be as you set them in previous run.