document contains answers to FAQ's regarding sales
related issues and product capabilities. For additional
product details, please see the individual product
descriptions in the product section of this site, and
download the demos that you are interested in. We also
provide detailed datasheets on-line, available for
downloading, in the Adobe Acrobat PDF format.
related queries should be sent to firstname.lastname@example.org,or directed to the sales
staff at (508) 359-6639.
The latest versions of our
products are as follows, for ALL compiler versions:
3D++, Data Analysis --> 1.0
Real-Time Tools ---------------------------->
Graphics Class Libraries ----------------> 3.0
RT Tools for DOS
SE Tools for DOS -------------------------->
There are many
differences inherant in an ActiveX vs. a DLL
library. Both versions of our products provide
very flexible, feature rich graphing capabilites,
but the programming interface used in each is
different. It is strongly recommended that you
download the demo for one of our ActiveX controls and
the demo for the corresponding Tool library and
investigate the similarities and differences.
talking with customers and potential customers we
have found that 98% of you are using Microsoft
products/compilers. There doesn't seem to be a
big enough market for OWL products to justify our
development efforts on them.
Yes. Since April
of 1996 both the Charting Tools and Real-Time
Graphics Tools for Windows products support
The GCL for MFC
support both 16-bit and 32-bits. It is an add-on
to either our Charting Tools or RT Tools product.
We currently offer
three different ActiveX controls:
Charting Tools ActiveX
Real-Time Graphics ActiveX
While we do not
have a version of the SE Tools for Windows NT and
VC++, we may have similar products to suit your
needs depending on what you are looking for. The Charting Tools for Windows is a DLL package
containing routines for producing many different
2D charts, such as those found in the SE Tools.
If you are interested in 3D charting, then the
similar product we offer for NT and VC++
development is our 3D++ Library product. Both of these
products are available for use with NT and VC++
4.2 and higher, and are also available as OCXs
(go to Products for more information).
If you are looking for numerical analysis
routines, such as those found in the SE Tools, we
have the Data Analysis ActiveX which might suit your
Our tools are
completely hardware independent, and do not
include any special drivers or direct hardware
support. You, as the programmer, are responsible
for provide new data values to our update
routines, in the form of floating point numbers.
Because a few
features in our C and Delphi versions are not
implemented in our VB RT Tools. For example, VB
has its own controls and event handling structure
built-in, so we don't supply our controls in the
VB version of the RT Tools. Other differences
between the versions include:
Functions - callback functions were not
supported by earlier versions of Visual Basic.
Therefore, the related callback functions for
alarm events, DDE, and Quinn-Curtis child
controls are not supported.
Objects - Visual Basic controls, such as
various button types and scroll bars, can be used
to provide essential input capabilities for
instrument interfaces. These VB Controls are used
in place of the Quinn-Curtis controls found in
the C and Delphi versions of the tools.
- DDE -
display data provided by a server application.
Only one DDE function is supported in the VB
version of the tools - WRConnectDDE.
Mouse Support - WGGraphMouseEvent is
found in the file VBRTHOOK.DLL. The source code
to VBRTHOOK.DLL is supplied in C and can only be
compiled using Visual C++ or Borland C++
Management - the user extension to the
page window procedure, WGUserPageProc, can be
found in the VBRTHOOK.DLL file. The user is free
to add message and command processing to this
Point Number Data Type - 8-byte double
format is supported.
No. Our Tools
support Windows platforms only, including,
Windows NT, Windows 95, and Windows 3.1.
Yes, the DLL does
handle multiple instances of applications of the
same type that use it.
We don't do any
special thread handling, but you can bring up two
separate applications that contain the same type
of graph and have them running at the same time.
In addition, you should put all parts of your
application that use the Quinn-Curtis DLLs into
the same thread.
If our calls are in a single thread, you can
still have other threads running that perform
different operations, but do not affect the QC
Yes. Our Windows
Tools provide built-in dialogs for editing chart
object characteristics which are invoked when the
mouse is used to select a graphical object.
currently don't contain any language support for
languages other than US English. Translation may
be possible, however. The key to a translation is
the conversion of all strings used for error
messages and translation of the dialog text. Also
any other resources should be checked as well.
The functions in
the RT Windows library and the RT DOS library are
similar, but none match exactly due to the
different nature inherant in Windows vs. DOS
programming. You do get almost all of the same
graphics capabilities in the Windows routines as
provided in the DOS library, and you do get
additional functionality built into the Windows
package. Many of the routines contained in both
are similar and do take some similar parameters.
For example, with both products, you need to
create a window and build a graph in it. In the
DOS product, you would call the rtsetupscrollgraph
routine to create a scrolling graph in a
window; in the Windows version you would call WRSetScrollgraph.
We provide many example programs on disk, as well
as shorter code examples in the printed
documentation, which will help you to get