Changeset 57


Ignore:
Timestamp:
Jul 15, 2013, 6:18:37 PM (12 years ago)
Author:
ataylor
Message:

Updated README.TXT for v1.20 GA release.

File:
1 edited

Legend:

Unmodified
Added
Removed

  • TabularUnified projects/vrobjex/readme.txt

    r56 r57  
    1111
    1212  README.TXT      This file.
    13   ICONBUTT.MTO    IconButton drag-and-drop information for VX-REXX designer.
    14   TABBEDDI.MTO    TabbedDialog drag-and-drop information for VX-REXX designer.
    15 | TOOLTIP.MTO     ToolTip drag-and-drop information for VX-REXX designer.
    16 | TTIPMTHD.VRM    Drag-and-drop designer macro used by TOOLTIP.MTO.
    17 | TTIPMTHD.VRW    Drag-and-drop designer macro used by TOOLTIP.MTO.
    1813  VROBJEX.DLL     The VX-REXX Extras library (developers and runtime).
    19   VROBJEX.INF     Online help & programming reference.
    20   VROBJEX.SYM     Symbol file for support.
    21   VROBJEX.VXO     Library loader for VX-REXX designer.
     14| DEVELOP.ZIP     The developer-specific files, zipped.  Contains:
     15  - ICONBUTT.MTO  IconButton drag-and-drop information for VX-REXX designer.
     16  - TABBEDDI.MTO  TabbedDialog drag-and-drop information for VX-REXX designer.
     17| - TOOLTIP.MTO   ToolTip drag-and-drop information for VX-REXX designer.
     18| - TTIPMTHD.VRM  Drag-and-drop designer macro used by TOOLTIP.MTO.
     19| - TTIPMTHD.VRW  Drag-and-drop designer macro used by TOOLTIP.MTO.
     20  - VROBJEX.INF   Online help & programming reference.
     21  - VROBJEX.SYM   Symbol file for support.
     22  - VROBJEX.VXO   Library loader for VX-REXX designer.
    2223
    2324
    … …  
    2930  from your system.
    3031
    31   You can safely ignore all other files from this package unless you plan to
    32   develop REXX programs using this library.
     32  You can safely ignore the remaining files from this package unless you plan
     33  to develop REXX programs using this library.
    3334
    3435
    … …  
    4142  the VXREXX directory.
    4243
    43   Copy VROBJEX.DLL to any directory on your LIBPATH.  Copy VROBJEX.VXO and
    44 | VROBJEX.INF to your VXREXX directory, and *.MTO, *.VRM and *.VRW to the
    45 | VXREXX\SYSTEM subdirectory.  Save VROBJEX.SYM anywhere you like, or ignore
    46 | it entirely - it is only needed if you want to analyze process dumps (and if
    47 | you don't know what that means then you almost certainly don't need it).
     44  Copy VROBJEX.DLL to any directory on your LIBPATH. 
     45
     46| Unzip the file DEVELOP.ZIP to your main VXREXX directory. This will place
     47| VROBJEX.VXO, VROBJEX.SYM and VROBJEX.INF in that directory, and the MTO and
     48| macro files in the VXREXX\SYSTEM subdirectory.  (Note that VROBJEX.SYM is
     49| only needed if you want to analyze process dumps - if you don't know what
     50| that means then you can safely ignore it).
    4851
    4952  Start VX-REXX and make sure that the new object classes appear on the object
    … …  
    8790  The above code is managed by VX-REXX itself, and not by the object class;
    8891  therefore, there is unfortunately no way to automate this task.
     92
     93
     94Using the ToolTip class
     95
     96| The ToolTip control actually consists of two PM windows which work in
     97| tandem.  The ToolTip object you create in the designer is a subclass of
     98| the descriptive text control (you are advised to set its Visible property
     99| to 0 as it has no interactive use).  This in turn creates a small secondary
     100| window which is used to display flyover help for any number of controls
     101| that you 'register' with the ToolTip object.  This secondary window is
     102| owned by the ToolTip control, but has the whole desktop as its parent; this
     103| arrangement allows it to extend outside the display area of the VX-REXX
     104| application.  The secondary window is automatically hidden, unhidden,
     105| resized, and updated with the correct text, as appropriate.
     106|
     107| Basically, you create one ToolTip object to manage all tooltips, then use
     108| its Register method to associate any number of other GUI controls with it
     109| in order to assign them tooltips.  The beauty of this is that works with any
     110| type of VX-REXX control (even the program window itself).  So you can add
     111| tooltips to buttons, dialogs, text fields, notebooks, sliders, containers...
     112| whatever.
     113|
     114| The only real restriction is that a ToolTip object must be on the same
     115| thread, and share the same message queue, as any other controls that it has
     116| registered.  (All controls in an application are normally on the same thread
     117| in any case, so this should not be an issue unless your program does some
     118| extremely unorthodox things.)
     119|
     120| All tooltips managed by a single ToolTip object will share the same font
     121| and colours.  If you want tooltips with different colours or fonts for
     122| certain controls, you will have to use separate ToolTip objects for them.
    89123
    90124
    … …  
    109143     method on the TabbedDialog in order to switch focus to the notebook tabs.)
    110144
     145| ToolTip control:
     146|  - Registering a control on one dialog window with a ToolTip control belonging
     147|    to a different window SHOULD work (as long as both windows are open at the
     148|    same time), but this has not been heavily tested.  In any case, doing this
     149|    is not really recommended.  (If you MUST do this, you should Deregister
     150|    any controls on a window whenever that window is closed, as trying to
     151|    track controls which no longer exist will waste time and resources.)
     152
    111153
    112154History
    … …  
    204246--
    205247Alex Taylor - alex at altsan dot org
    206 June 2013
     248July 2013
Note: See TracChangeset for help on using the changeset viewer.