New Features in Panther 5.30
Windows, Character Mode, Motif
38146 – Trace
Log Feature, ability to trace events such as JPL
execution, database calls. Event information can be written to a trace file as
they occur.
38167 – File type is pre-set in the Library Table of Contents window if Save
Preferences on Exit is selected.
38060 - JDK 6 Support.
38062 – Native 64bit Windows port (Win).
38069 – Tooltips now appears for toolbox (Linux).
38093 – Improved link parameters.
38096 – Support for all 6 arguments in the installed prototypes functions.
38101- Ability to center sm_message_box dialog in MDI frame/screen (Win,
Motif).
38106 – Increase Max Size of JPL Arrays to 1,052,688 for a variable of 255
characters in length.
38107 - Access to Panther setup variables from smvars files using Property
API.
i.e. @app->java_use, or @app->smpath etc.
38109 – Visual Studio 2010 support (Win).
38229 - Support for Operating System Authentication in Oracle
Report Writer
38138 – Support for tiff image using PDF Driver.
Databases
38094 – Short Escape
sequence support for ODBC is now the default.
38147 - Sybase 15 Support.
38088 - Support
access to Oracle CLOB (character large object) columns. See below.
Library Functions
38132 - sm_mw_DismissIntroPixmap() allows one to close IntroPixmap window.
38183 - sm_d_jplpublic and sm_n_jplpublic, load JPL modules
from memory .
38210 - sm_com_attach() ability to attach to an active COM object’s
process.
38808 - dm_ora_clob_update()update a CLOB (character large object)
column after selecting the column.
retcode = dm_ora_clob_update (cursor_name, column_number, field_name);
int retcode; returns 0 or an error code
char *cursor_name; name of the cursor
int column_number; number of column in select list
char *field_name; name of the wordwrap field holding the data to write to the
CLOB
Panther 64-bit for Windows
1. Panther 64-bit for Windows provides 64-bit libraries and executables to be used on 64-bit Windows operating systems. Although Panther 32-bit for Windows may be used on 64-bit Windows operating systems, Panther 64-bit must be used when linking with third party 64-bit libraries. For example, use Panther 64-bit if 64-bit Oracle Client libraries are required. The only 32-bit components that may be used with Panther 64-bit are COM and ActiveX components.
2. All file names that had the suffix “32” for Panther 32-bit are replaced by file names using “64” as their suffix for Panther 64-bit. For example, “prol5w64.ini” is used instead of “prol5w32.ini.” This is a change from Panther 5.20 64-bit. (Note that Panther 64-bit for Windows had a limited release as a late addition to Panther 5.20.)
3. A native MS SQL driver is not supported in Panther 64-bit. Use the ODBC driver instead.
4. Panther 64-bit can create containers for existing ActiveX components as well as access COM objects, but cannot be used to build COM Components. Panther 64-bit does not support Microsoft Transaction Server (MTS) or COM+.
5. The Panther Editor and runtime for Panther 64-bit require ‘msvcr80.dll’, a Microsoft Visual C++ 2005 redistributable file, as well as its manifest, ‘Microsoft.VC80.CRT.manifest’. These files are installed in the ‘util’ directory, and should be redistributed with Panther 64-bit applications. Install these two files in the same directory as any executables for Panther 64-bit end-user applications.