ICS MotifZone

If you received a CD in the mail, please read this section. If you downloaded an evaluation, please see the section called Installing from a Download.

Contents of the CD-ROM

The CD-ROM contains the following files and directories:
File Description
./install.txt Text version of these notes
./install.pdf Adobe Acrobat version of these notes
./manifest Text file identifying product(s) contained on the CD-ROM
.// One or more product installation directories. See the file ./manifest for descriptions
./goodies/ Directory with various software that you might find useful.

Quick Start

1. Mount the CD-ROM
2. Change to the directory on the CD-ROM that contains the product you want to install.
3. Review any readme, license, release.txt, and change.log files you find in the directory.
4. Execute the setup program and follow its instructions:
   % ./setup

Mount the CD-ROM

If your system does not automatically mount the CD-ROM, mount it using the instructions below.

1. Become the superuser.
2. Mount the CD-ROM using the command below that matches your system:
   OS Mount Command
   AIX %mount -r -v'cdrfs' /dev/cd0 ${mount-point}
   HPUX %mount -r -F cdfs /dev/dsk/c0t3d0 ${mount-point}
   IRIX %mount -t iso9660 /dev/dsk/dks0d1s7 ${mount-point}
   SunOS %mount -o ro -t hsfs /dev/sr0 ${mount-point}
   Solaris %mount -o ro -F hsfs /dev/dsk/c0t6d0s0 ${mount-point}
   Tru64 %mount -r -t cdfs /dev/rz4c ${mount-point}
   Linux %mount -t iso9660 /dev/cdrom ${mount-point}

Notes:

1. ${mount-point}refers to the location in the file system that you want the CD-ROM to be mounted.
2. The specific device files above (e.g., /dev/rz4c) are just examples. Please check with your system administrator for the specific device file to use.
3. When done, you can unmount the cdrom using the command:
   % umount ${mount-point}

Installation

Your CD-ROM will contain one or more directories. Each directory will be the name of the ICS product. The text file ./manifest describes each product contained on the CD-ROM and identifies the associated directory. To install a specific product, follow these instructions.

1. Become the superuser (if you are not already).
2. Change directory to the appropriate product directory ().
   % cd ${mount-point}/
3. Read the file license contained in this directory before proceeding. Do not install the software if you are not willing to agree to the terms of this license. You might also want to read any readme or change.log files provided in the directory too!
4. Execute the setup command and follow its prompts.
   % ./setup

Note: There is a known bug with SGI evaluations of Builder Xcessory that is fixed in the next release. For now, if you are evaluating Builder Xcessory on SGI, please see the question: Why does my BX Evaluation on SGI always start up in Demo mode? and then proceed with step #3 below.

Full operation of a BX PRO evaluation requires the installation of two evaluation license keys: one for Builder Xcessory and one for the bundled libraries (EPak and ViewKit). You should have received a separate email with both keys. If you did not, you can request another evaluation key at . The following instructions will help you properly install the keys.

1. Start BX by typing the following at the shell prompt:
   % bx
2. BX will startup and ask you for a license key. Open up the email containing the key and copy-paste it into the text entry field. If you do not yet have your key, you can click Cancel and continue in "Demo Mode" (i.e., you cannot save any user interfaces). BX will keep asking you for the Key on every startup until you install a Key.

   Note: The evaluation key format differs between Linux and UNIX. If you are installing a Linux evaluation key, it should look like (it is a single line, ignore any line breaks):

   LICENSE BuilderXcessory (key)

   And a UNIX evaluation key should look like (again a single line, ignore any line breaks):

   FEATURE BuilderXcessory ICSBX 6.000 (Date) (#licenses) (key) "ICS Builder Xcessory" DEMO

   Where (key), (Date), and (#licenses) are replaced by values appropriate for your environment. When asked to enter the Evaluation Key, enter the whole line starting with "LICENSE" for Linux and "FEATURE" for UNIX. It is highly recommended that you copy and paste the appropriate line from the email containing the key to avoid re-typing mistakes.

   Note: The Builder Xcessory evaluation key is stored in a subdirectory of ~/.builderXcessory6. This means that every person evaluating Builder Xcessory must install this key through the dialog box mentioned above. You do not need to request additional evaluation keys. The one that you used will work for them too.

3. The EnhancementPak and ViewKit libraries included with the BX PRO eval, also require a key to run applications. You can build an application using EnhancementPak widgets or the ViewKit Library, and you can even generate code, compile it and link it. However, when you try to run your application, a Dialog Box will appear and a Key will be requested (both EnhancementPak and ViewKit are enabled by the same Key). If you don't enter a key, the application will be terminated.

   Note: If you wish to avoid entering the EnhancementPak/ViewKit evaluation license key every time your run your test application, then simply make sure that the following commands are executed in the shell (or shell script) that runs your application:

   For csh (and its variants):
   % setenv ICS_EVAL_KEY (widget libraries evaluation key)

   For sh (and its variants):
   % export ICS_EVAL_KEY=(widget libraries evaluation key)

Possibly, but not likely. Typically, a key is not recognized for one of the following reasons:

1. On UNIX, you have installed a BX 6 key and a BX 5 key is still in the FlexLM database. (See next question)
2. A UNIX key is used for Linux (or the opposite). Linux keys start off with the word "LICENSE" while UNIX keys start off with the word"FEATURE".
3. Some email readers wrap lines and only half the line gets pasted into the text field.
4. People try to rearrange a Linux key to look like the example UNIX key that the dialog box requests (This is a bug in BX 6.0. In BX 6.1, the example used for Linux will be a Linux key, and the example used for UNIX will be a UNIX key).
5. You have put the License file in a non-default location and have set the wrong environment variable. UNIX and Linux use different environment variables to specify the location of the license file. See the question How can I put the license file somewhere else? for details.
6. If all else fails, remove the .builderXcessory6 directory in the user's home directory and try starting bx again. (It stores the license key in a file in the .builderXcessory6 directory and if you have a bad key, it will generate the error message you received.)

On UNIX platforms, ICS uses the FlexLM license server to manage the floating licenses to BX. When you purchase a new license or an upgrade license, you use commands provided by FlexLM to add these licenses to the database of the license server. This process can be confusing, and we highly recommend that new users carefully read Appendix C: License Manager, before adding attempting to add new or upgrade licenses.

In the situation described, the most likely problem is that you forgot to remove the BX 5 licenses from the FlexLM license server. A BX 6 license key will enable both BX 6 and all prior releases of BX (e.g., BX 5, 4, 3.5.1, etc.) to function in "Full Use Mode". However, when BX 6 checks out a BX 5 key, it rejects it and goes into "Demo Mode". This explains the observed situation where BX 5 works, and BX 6 does not.

No. Cut the line from the email that delivered the key and paste the exact line into the entry field. The example license line is accurate for UNIX evaluation licenses.

The environment variables ICS_LICENSE_FILE (on Linux platforms) and LM_LICENSE_FILE (on UNIX platforms) are used to specify the location of the BX PRO license file. To set the environment variable

Linux:
For csh (and its variants):
% setenv ICS_LICENSE_FILE /some_path/mylicensefile.dat

For sh (and its variants)
% export ICS_LICENSE_FILE=/some_path/mylicensefile.dat
UNIX:

For csh (and its variants):
% setenv LM_LICENSE_FILE /some_path/mylicensefile.dat

For sh (and its variants)
% export LM_LICENSE_FILE=/some_path/mylicensefile.dat

BX 6.1: Yes, just cut and paste the appropriate key into the key request dialog box as BX starts on the platform. Alternatively, if your startup file detects which system type you are using, just set the environment variable above to the appropriate location for that system. EPak and ViewKit share the same evaluation key on both Linux and UNIX, so you can just set it once.

BX 6.0: If you need to evaluate both a UNIX and Linux version of BX PRO with BX 6.0, do the following:

Linux: Copy your license into a file called icslicense.dat and save this file into your home directory.

UNIX: Start BX on your UNIX system and copy and paste the UNIX evaluation key into text box when it requests a license.

You need to manually set the number of file descriptors in the shell that starts the lmgrd daemon to something less than 4096. Our suggestion is to use 1024 since that was the default on Solaris 7 systems. To do so:

For csh (and its variants):
% limit descriptors 1024

For sh (and its variants)
% ulimit -H -n 1024

Restart the lmgrd and do a:
% ps -ef

You should see the ICSBX daemon running.

BX is known to crash when run on RH Linux 7.3 if the environment variable LANG is set to en-US.iso885915 and you are running BX on a foreign X server. More information on this bug in Red Hat can be found https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=62844. To work around it, please set your environment variable LANG to en_US. For example, if you are using the csh shell you would type:
% setenv LANG en_US

After installation, I run BX on SUN Solaris, but I got an error message like: bxb: fatal: libCrun.so.1 version 'SUNW_1.2' not found.
You need to install a patch on your system. They are available from Sun.com web site. The patch numbers are

108434-17 (if you are using Solaris 8)
111711-11 (if you are using Solaris 9)

These patches will provide the libraries that are needed by BX.

BX PRO 6.0 is only compatible with Open Motif 2.1. If you are running Red Hat 7.3, the default version of Open Motif is 2.2. You need to install the Open Motif 2.1 compatibility library that can be found elsewhere on the Red Hat 7.3 distribution. If you cannot find it, and you have a CD based evaluation, then you can use the RPMs found on the CD at: /ome-compat/ (alternatively, they may exist at: /bxe6lin/ome-rpms/) If you downloaded your eval, see the suggested sources for Open Motif provided in the next question.

BX PRO 6.1 is compatible with Open Motif 2.2 on Red Hat 7.3+ and is configured to use Open Motif 2.1 on Red Hat systems prior to Red Hat 7.3. If you have change Open Motif versions, make sure that you install a compatible version of BX PRO.

ViewKit is a C++ library and because of the implementation of the C++ language, is dependent on the specific version of the C++ compiler you are using. If you use libraries built with one C++ compiler, and you try to link those C++ libraries with code or libraries generated with another compiler, you will get link errors at best, and in the worst case, puzzling runtime errors. In some cases, even "minor" releases in the C++ compiler can create incompatibilities (e.g., gcc 2.95 and gcc 2.96 are NOT compatible!) ICS provides ViewKit for a wide variety of C++ compiler releases. So when you install, make sure that you pick the one that matches the particular release of your C++ compiler!

The compiler released use to build ViewKit is encoded in the name of a file that starts out with vkcompiler.{compiler version}. For example if you installed ViewKit for Solaris and the Sun Cxx 4.2 compiler on your system, then you would see in the install directory (typically /opt/bxpro-6.0/lib) the files:

vkplatform.sparc-solaris-2
vkcompiler.suncxx4.2

When the ICS installer runs, it creates a log file in /tmp. If your installation fails, or you appear to be missing the actual bx shell script, this log should provide you with a clue to the problem. The format of the file is:

icsInstal-mm-dd-1yy.log

This file can be cryptic. So if the problem is not obvious, please send it to ICS along with your problem report.

Builder Xcessory provides a comprehensive set of tutorials. They are also in pdf form and also accessible from the BX Help menu. The easiest way to get started with BX , is to try the first three-four tutorials and start using BX immediately.

You can select or unselect an entire hierarchy of widgets by holding the Shift key and selecting the top widget in the hierarchy in the Browser. You can also select an entire hierarchy of widgets in your user interface by using the lasso-selection. Select the container and its children by holding the Shift key while dragging a box around the manager using MB1. Then move the selected group using MB1.

When you place an object in Builder Xcessory, you implicitly provide a width and height for the object. If you don't want to set the width and height, use the Natural Size action from the Main Window Edit menu or from the MB3 Quick Access menu in the Browser Tree or on the object itself. By setting Natural Size, the child widget will automatically adjust to changes in the size of its parent.

Sometimes it is difficult to zero in on the exact drop site when adding a widget to your user interface. For example, when adding a pushButton to a cascadeButton, it is easy to miss the drop site and end up with the pushbutton parented to the wrong widget. In cases like these, it is usually much easier to select the widget on the palette with MB2 and then drop it on the desired parent widget in the Browser. If you prefer the WYSIWYG approach, then the next question on Keep Parent might be a solution.

First, let’s explain why this error message is generated.

When you request BX to set a resource, it sets the resource using the standard XtSetArg routine. It then reads the value of he resource back using the standard XtGetArg function. If the values read back do not match the new values, BX generates the error message "Widget Does Not Allow Resource to be Modified at this Time". Basically, this error message means that the Motif toolkit you are using is not allowing the resource to be set.

In many cases, the situation stems from the fact that you are trying to change the physical dimensions of a child widget where its geometry is actually being overridden by the Parent object. For example, it is very common for this error message to occur when you have parented a XmFrame to an XmForm, set the attachments, and then try to resize directly the XmFrame (we do this in Tutorial 3!). You can get around this in a couple ways. In many cases, it is easiest to grab the user interface with the Window Manager and directly resize the window. In other cases, you will need to unhook the various Attachments, resize as desired, and then reestablish the attachments.

This error message might also be generated in cases where you need to set the values of multiple resources at the same time. For example, in ICS’s EditTable widget, you need to set the number of rows and columns at the same time. You can’t just change the number of columns without setting the number of rows too. It is common for users to try to change the number of columns in the resource editor and receive this error message. Since you cannot change the number of rows and columns simultaneously from within the BX resource editor, you have to apply a different strategy to set the resources appropriately. Basically, you create a "style" that has the number of columns and rows set to the desired value. You then apply this style to your EditTable widget and both rows and columns get set simultaneously and the widget is happy. This strategy can also be applied to other widgets that have similar constraints.