.

Release Note
Motion Scope

Motion Scope Version
MPI Release
Release Date
02.00.01
04.00.01 – 04.00.xx
NA
02.00.00
31Jul2009

  Table of Contents
    New Features
      Version 02.00.00
Precision Parameters for X and Y Axis Labels - 661
       
    General Changes
      Version 02.00.01
Next Available Recorder - 1501
       
    Fixed Bugs
      Version 02.00.01
MotionScope should use MEI_MDK_DIR in which to create the INI file - MT1516
       
    Limitations
      Version 02.00.00
Tab Navigation Does Not Work As Expected In Motion Scope - 1457

New Features

02.00.00

  Precision Parameters for X and Y Axis Labels
    Reference Number: 661
    Type: New Feature
    Motion Scope Version: 02.00.00
    Description:
Precision parameters for X and Y axis labels are now available through:
– Trace Edit dialog for Y axis labels
– Pane Display Settings for X axis labels
In addition to the axis labels, these apply to the Ctrl-LMB cross-hair values display.

The precision values default to 9 for 32-bit and 20 for 64-bit data types.
These values persist from session to session in the initialization settings.

The precision value supplied in the dialogs is an integer and specifies the parameter to be supplied in the printf() calls using the "%.*g" parameter.

The meaning of the "%g" data type parameters is: Signed value printed in f or e format, whichever is more compact for the given value and precision. The e format is used only when the exponent of the value is less than –4 or greater than or equal to the precision argument. Trailing zeros are truncated, and the decimal point appears only if one or more digits follow it.

The meaning of precision in this context is The precision specifies the maximum number of significant digits printed.

Unfortunately, the precision parameter is not applied to the control bars which display the YScale, YOffset, XRange, and XOffset. These use the default precisions described above.

General Changes

02.00.01

  Next Available Recorder
    Reference Number: 1501
    Type: Change
    Motion Scope Version: 02.00.01
   

Description:
When a new pane is created or an existing pane is intialized, Motion Scope would take the next recorder number in it's own recorder number list. If another application had previously reserved the recorder, then Motion Scope could potentially use the same recorder number as the other application.

To prevent conflicts between applications, Motion Scope now checks for the next available (non-reserved) recorder.

Limitations

02.00.00

  Tab Navigation Does Not Work As Expected In Motion Scope
    Reference Number: 1457
    Type: Limitation
    Motion Scope Version: 02.00.00
    Description:
When the Traces button is chosen from the main window, the tab key cannot be used to navigate to different controls. For this same dialog box, arrow-key navigation does not work.

For the dialog box accessible by using Traces -> Select Traces Set Window -> New -> Choose New Trace Type Window -> All Others (User Defined), two tabs are needed to navigate to the next control when the next control is in a different group box.

The Edit trace group transition from Data type to Auto scale box needs only one tab while other boxes need two tabs.

Pane Display settings Label precision can never be reached by tabbing.

Fixed Bugs

02.00.01

  MotionScope should use MEI_MDK_DIR in which to create the INI file
    Reference Number: MT1516
    Type: Fixed Bug
    Motion Scope Version: 02.00.01
   

Problem:
MoScope exits with a pop-up error message indicating that it cannot create the INI file.

Cause:
Instead of using MEI_MDK_DIR to create the INI file, MoScope uses %userprofile%. The %userprofile% defaults to C:\WINDOWS which the user may not have access to.

   

Fix/Solution:
MoScope uses MEI_MDK_DIR to create the INI file instead of %userprofile%.

   

Affects to Application Code:
INI file is created without errors.

       Legal Notice  |  Tech Email  |  Feedback
      
Copyright ©
2001-2010 Motion Engineering