Quest® XRT PDS
Version 2.3.0
Release Notes
January, 2007
Resolved Issues and Enhancements
Quest Software's XRT Professional Developer's Suite (PDS) integrates our six most popular Motif widget products into a single, easy-to-use, affordable suite. XRT widgets are used by tens of thousands of professional developers around the world to build informative, attractive and functional user interfaces.
XRT PDS is composed of the following products:
| XRT/3d | A powerful three- and four-dimensional graph component that displays a scalable and rotatable 3D surface, optionally containing contours and zones. Scatter plots can also be drawn. |
| XRT/field | A useful package of type-specific text entry components that can validate and convert their data, plus combo box, spin box and calendar widgets that make it easy for users to select an item from a list of alternatives or a date from a day grid. |
| XRT/gauge | XRT/gauge includes seven highly customizable dials and gauges Motif widgets that measure and display the value of a property or attribute. |
| XRT/gear | A collection of widgets and utilities that make your applications more visually appealing, intuitive and easy to use. |
| XRT/graph | A highly flexible two-dimensional graph component that lets you add plots, area graphs, bar, stacking bar, pie charts and others to your applications. |
| XRT/table | An adaptable table component that lets you display text, pixmaps and widgets in a tabular format that users can edit, scroll or resize. |
| XRT/pageformatter | A set of methods and procedures for adding paginated, formatted, flowed text and image output to UNIX applications. |
| MVC Kit for XRT Widgets | Software that lets you easily create multiple dynamic views of a single set of data in XRT/graph, XRT/table or XRT/3d. |
| Integrations | Integrations with all popular GUI Builder tools, including Builder Xcessory, TeleUSE, UIM/X, X-Designer and SPARCworks/Visual. |
PDS includes a full set of over 1,800 pages of printed documentation, all available online in Acrobat PDF format.
The following is a list of issues addressed and enhancements implemented in this release of XRT PDS.
|
XRT Product |
Resolved Issue |
Change Request |
| XRT/PDS |
Problems capturing PNG images from screen depths other than 8 bit. |
CR#31379 |
|
XRT widgets leak serverside resources (Pixmaps, Cursors, GCs). |
CR#52547 |
|
|
Some XRT widgets would not trigger XmNhelpCallbacks registered on them. |
CR#45766 |
|
|
XRT/3d |
XRT/3d legend does not display all ranges with user defined distribution tables. |
CR#52545 |
|
When zoomed in on an XRT/3d graph, the legend displayes the labels with the wrong colors. |
CR#52547 |
|
|
Printing the widgets on x86_64 Linux causes segmentation fault. |
CR#52718 |
|
|
XRT/field |
Drag and drop does not work on Solaris 7 with Motif 2.1. To use the version with the fix for this bug, ensure you are using the XRT PDS 2.3.0 Motif 2.1 build. You may then only link your application with Motif 2.1 libraries. |
CR#15582 |
|
XRT/field combo box dropdown menul now handles X events the same way as the Motif menus, and does not block custom made event loops |
CR#15731 |
|
|
When tabbing to a new field, the cursor does not show as inactive when using Motif 2.1. To use the version with the fix for this bug, ensure you are using the XRT PDS 2.3.0 Motif 2.1 build. You may then only link your application with Motif 2.1 libraries. |
CR#19258 |
|
|
Cannot override right and left arrow translations on an XRT/field spinbox. |
CR#36115 |
|
|
When linking against Motif 2.1, the scrollbars in an XRT/field widget do not scroll the full area of the field's text. |
CR#39601 |
|
|
Free Memory Reads reported in XRT/field widgets. |
CR#44655 |
|
|
XRT/gear |
Hitting the shortcut key deselects current node in an XRT/gear outliner when in multiple selection policy. |
CR#20404 |
|
XRT/gear widget snapshot sometimes fails to take snapshots of XRT/table widgets. |
CR#27339 |
|
|
Inconsistent behavior exists with XRT/gear outliner node selection and de-selection functionality. |
CR#27501 |
|
|
XRT/gear Enhanced Togglebutton does not accept setting of selected color resource to "black". |
CR#31121 |
|
|
Allow any pane with in an XRT/gear paned window be defined to be the default to be expanded to fill space created by interface resizing. |
CR#31935 |
|
|
XRT/gear Tab Manager does not properly inherit XmNactivateCallback and XmNarmCallback callbacks. |
CR#32064 |
|
|
XRT/gear Outliner became unstable and prone to crashing after combinations of selecting, collapsing nodes, and scrolling to select a new node. |
CR#33574 |
|
|
XRT/gear Enhanced Pushbutton does not update properly on setting of resource XmNlabelString. |
CR#33653 |
|
|
XRT/gear Outliner suffers from memory leaks when destroying a tree of lightweight nodes. |
CR#33763 |
|
|
Horizontal Scrollbar in XRT/gear Outliner does not properly update with addition and removal of columns. |
CR#33902 |
|
|
XRT/gear Outliner does not properly sort nodes given a user defined sort function on NuTCRACKER and HPUX builds. |
CR#34248 |
|
|
Not receiving a SELECT_END callback when setting doit=false in a Selection callback in XRT/gear Outliner. |
CR#34926 |
|
|
Memory leaks occur when destroying an XRT/gear Outliner widget. |
CR#35135 |
|
|
XRT/gear Enhanced Pushbutton does not appear unselected when you move the mouse off the widget. |
CR#35327 |
|
|
In XRT/gear Tab Manager, Ctrl-Button 1 on a tab button should move the focus, but not change tabs. |
CR#35454 |
|
|
XRT/gear Outliner displays clip arrows on cells when there is no content to be clipped. |
CR#36711 |
|
|
XRT/gear Outliner can override translations which are set in a resource file for it. |
CR#37352 |
|
|
XRT/gear Widget Tips keeps an extraneous event loop running after the tip has disappeared. This prevents custom XEvent loops from running. |
CR#39014 |
|
|
XRT/gear Outliner should unselect a node that is Ctrl-clicked on when in selection policy MULTIPLE_AUTO_UNSELECT. |
CR#39252 |
|
|
XRT/gear Combo Box menu will not pop down in certain occasions. |
CR#40407 |
|
|
XRT/gear Outliner suffers from memory corruption problems. |
CR#45209 |
|
|
Some XRT/gear Tab Manager resource converters do not function properly on Linux, gives message: "Warning: Cannot convert string "1" to type GearActivePageNumber." |
CR#47967 |
|
|
Printing widgets on x86_64 Linux cause segmentation faults. |
CR#52719 |
|
|
XRT/graph |
XRT/graph widget causes XError if the graph area is forced to be drawn too narrow. |
CR#31940 |
|
Zooming in on an empty graph causes Floating Point Exceptions when data is added to the widget. |
CR#38474 |
|
|
Printing widgets on x86_64 Linux cause segmentation faults. |
CR#50364 |
|
|
Point in an empty set can incorrectly appear in the graph at (0,0). |
CR#53234 |
|
|
XRT/pageformatter |
Printing on x86_64 Linux causes segmentation fault. |
CR#52722 |
|
XRT/table |
Values from different cells can flash into XRT/field widgets in an XRT/table when traversing between cells. |
CR#28847 |
|
On Solaris, XRT/table would lose focus from the current cell if it was programmatically updated |
CR#34676 |
|
|
No SELECT_END callback is called after the previous selection action is disallowed via a doit=False in the selection callback. |
CR#38695 |
|
|
Memory leaks and segmentation faults when pasting content to a non-selected, partially exposed cell. |
CR#38695 |
|
|
Click count is not reset when using keyboard traversal immediately after multi-clicking on a cell. |
CR#40733 |
|
|
XrtTblSetAllCursors, XrtTblRestoreAllCursors do not immediately update the current cursor. |
CR#45211 |
|
|
Printing widgets on x86_64 Linux cause segmentation faults. |
CR#52723 |
If you installed any previous version of XRT PDS, you may install XRT PDS 2.3.0 over top. There are no changes to the widgets requiring rewriting of existing application code. However, you will need to recompile and relink your applications in order to use the updated libraries.
Before installing XRT PDS 2.3.0, ensure your system meets the following minimum hardware and software requirements:
| Architecture | Operating System Levels Supported | Notes |
| Alpha | HP/Compaq Tru64 Unix 4.x, 5.x | |
| HP PA-RISC | HPUX 11.x | Both 32 bit and 64 bit architectures are supported |
| IBM RS6000 | AIX 5.x | Both 32 bit and 64 bit architectures are supported |
| Intel x86 | Any Linux distribution with glibc 2.3+, Solaris 2.6,7,8,9,10 | OpenMotif 2.1.30 and OpenMotif 2.2.x are supported in different builds for Linux |
| Intel IA64 | Any Linux distribution with glibc 2.3+, HPUX 11.22+ | Linux and HPUX are supported in different builds |
| AMD x86_64 | Any Linux distribution with glibc 2.3+ | |
| SGI | Irix 6.5 | Both 32 bit and 64 bit architectures are supported |
| Sun SPARC | Solaris 2.6,7,8,9,10 | Both 32 bit and 64 bit architectures are supported, separate builds exist for Motif 1.2 and 2.1 |
XRT PDS Requires up to 200 MB Hard Disk Space, depending on the installation platform.
The XRT PDS release package contains the following products:
This section describes installing XRT products from CD-ROM.
Applications built with XRT products are in one of three states:
XRT product licenses are sold on a per-CPU or per network-site basis. Per-CPU licenses authorize use of the XRT product on a particular CPU, identified by its CPUID. When you are using a Per-CPU license, you must link and authorize your application on the licensed CPU. (For shared libraries, you must authorize your library and link your application on the licensed CPU).
If you have purchased a network-site license, you will be supplied with a password which will enable one machine on your network to run the xrtld (XRT License Daemon). xrtld enables xrt_auth to work on all machines on the network. The purchase of a network-site license only licenses those CPUs on the same network and in the same building as the network-site license server. Please read and understand your XRT Product License Terms and Conditions which are printed in the front of each XRT product manual.
Installing an XRT product consists of the following steps:The XRT product you are installing will reside entirely within a single directory tree for each architecture, called XRTHOME. Before proceeding with the installation, decide where you want to install the product.
XRT products for the same architecture should be installed in the same directory. For example, XRT/graph for Motif (Sun SPARC) and XRT/table for Motif (Sun SPARC) should go into the same directory.
If you are installing products for more than one architecture, those products must be installed in separate directories. For example, XRT/graph for Motif (IBM RS6000)(Sun SPARC) should be installed in separate directories.
XRT products are supplied as compressed files (in a proprietary format) on the CD. They are installed by running an installation shell script on a machine with write-access to what will be the XRTHOME directory. If this machine does not have its own CD-ROM drive, it will need to remotely access a CD-ROM drive somewhere on the network. To install XRT product(s):
cd /cdrom sh install.shOn HP-UX systems, the install.sh file may have ;1 appended to the filename; you should add \;1 to run the installation shell script (for example, sh install.sh\;1). Also, on some systems, install.sh may appear in upper case.
The shell script presents a menu, listing the steps involved in installing an XRT product. Go through each step, answering the prompts presented. When the script has the information it needs, it will extract the XRT product(s) into the XRTHOME directory you specify. You can also install one or more passwords with the installation shell script, if you wish.
mkdir $XRTHOME DIR/doc cp -p *.pdf $XRTHOME/doc
After successfully installing the XRT product(s), you must ensure that all potential users of the XRT product(s) define the XRTHOME environment variable, and put $XRTHOME/bin on their search path. End-users running applications built with XRT products do not need to set XRTHOME.
For example, if XRT/graph is installed in /usr/xrt, csh users might put the following two lines into their .cshrc file:
setenv XRTHOME /usr/xrt set path=($XRTHOME/bin $path)
You can install or re-install a password at any time. You should install a password if you did not do so in Step 1, or if you have upgraded from an evaluation license to a permanent license. Each password is supplied separately. To install a password manually:
xrtpasswdYou will be prompted for various information including your serial number and password.
xrtpasswd will add your password information to the file $XRTHOME/etc/licenses. You may add passwords for multiple XRT products, multiple CPUIDs and/or multiple release levels into the same file.
If you've installed a disabled or time-limited version of an XRT product, and later purchase a permanent XRT product license, you will receive a permanent password. Use the xrtpasswd command to install your permanent password. After the password is installed,be sure to:
If you have purchased a Single license, skip this step. If you have purchased a Network-Site license, you must start the xrtld network license daemon on the machine designated as the XRT Network License Server. To do this:
XRTHOME={directory where XRT distribution is installed}
export XRTHOME
if [ -f $XRTHOME/bin/xrtld ]; then
$XRTHOME/bin/xrtld
echo XRT license daemon started
fi
If you have purchased static libraries, skip this step. If you have purchased shared libraries, you must now license each library you have purchased. If you have purchased an XRT PDS license you must authorize all five product libraries. Use xrt_auth to authorize shared libraries. For example, for XRT/table on SPARC Solaris:
cd $XRTHOME/lib-shared $XRTHOME/bin/xrt_auth libxrttable.soNote that the shared library name may be different on your architecture. You may also need to add $XRTHOME/lib-shared to your LD_LIBRARY_PATH or equivalent environment variable on your system.
Licensing Shared Libraries on AIX
On AIX, you cannot directly authorize the shared library. You must extract the single shared object file in the archive, authorize the shared object file, remove the old archive, create a new archive with the authorized shared object file, and then remove the shared object file. For example, for XRT/table:
cd $XRTHOME/lib-shared chmod 666 libxrttable.a ar x libxrttable.a libxrttable.o $XRTHOME/bin/xrt_auth libxrttable.o rm -f libxrttable.a ar rv libxrttable.a libxrttable.o rm -f libxrttable.o
Network-Site Licenses and Shared Libraries
For those with network-site licenses, once you've authorized the libraries the license daemon (xrtld started in Step 4) is no longer needed and can be killed. If you update your shared license, you will need to have the license daemon running in order to re-authorize your libraries (with xrt_auth).
A PPD file provides a list of options for a particular printer and the code to enable those options. By default XRT/pageformatter will install a few example PPD files supporting more popular Level 2 PostScript printers. You will, however, find a file on the CD called printers.ppd that contains a larger sampling. This is a compressed tar file. To install the additional PPD files, uncompress and then untar the file into your $XRTHOME directory. For example, the following commands with create the appropriate subdirectory:
cd $XRTHOME zcat < /dev/cdrom/printers.ppd | tar xvf -
XRT/pageformatter is made aware of what PPD file to parse by a file you need to create called printers in $XRTHOME/lib/ps. XRT/pageformatter will not install it. You need to create this file yourself. Using a text editor, create a printers file in $XRTHOME/lib/ps. In the printers file you can insert the name of the printer and its corresponding PPD file. For example:
ps hp5m1_v1.ppd ps2 hp4m3_v1.ppd
When you create a PostScript printer object, XRT/pageformatter will scan the printers file for a printer name matching the name of the Printer object, or your PRINTER environment variable. XRT/pageformatter will then search for the indicated PPD file in $XRTHOME/lib/ps/ppd, /usr/lib, /usr/lib/ps, /usr/local/lib, and /usr/local/lib/ps. If XRT/pageformatter finds the indicated PPD file, it parses it to determine the available options and default settings.
You can test the installation by copying the source for one of the products demonstration programs to a writable location, making it(type make if you've installed static libraries and make shared if you've installed shared libraries), and running it:
Note that for each product there are also examples in $XRTHOME/src/product/examples.
| info@quest.com | |
| Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA |
|
| Web |
Refer to our Web site for regional and international office information.
Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract.
Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com.
From SupportLink, you can do the following:
View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures.
The guide is available at: http://support.quest.com/pdfs/Global Support Guide.pdf.
This document contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaserâs personal use without the written permission of Quest Software, Inc.
© 1999 Quest Software, Inc. ALL RIGHTS RESERVED.
Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Fastlane, Final, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, Knowledge Xpert, LeccoTech, LiteSpeed, LiveReorg, Matrix Insight, Matrix.Net, MIQ, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Speed Change Manager, Speed Coefficient, Spotlight, SQL Firewall, SQL Impact, SQL LiteSpeed, SQL Navigator, SQLab, SQLGuardian, SQLProtector, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.
If you have any questions regarding your potential use of this material, contact:
|
Quest Software World Headquarters
LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 Email: legal@quest.com |
The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.