|
|
November 1999 |
|
More Information About Magic Version 8.30
(updated with Service Pack 2) |
|
|
|
|
|
Dear Developer,
We are happy to introduce Magic Enterprise Edition Version 8.30 updated with service pack 2.
Version 8.30 introduces new features and additional bug-fixes. Please
refer to the publication The Magic Guide to What's New in Version 8
and to other online help and printed documentation for a description of
the new functionality.
To find out more about the bug fixes and new features that were introduced by Magic Service Pack 1
and Service Pack 2, Please refer to the readme of Service Pack 2 release 830sp2.htm on your CD.
We hope you will find working with the product enjoyable and
fruitful.
Please read the following for additional information on this
version:
New Features in Version 8.30:
Magic Web Online
HTML Merge New
Wallpaper Task
Execution Repository Parameter Description Flow Monitor in Background mode Magic Broker added functionality
Additional Remarks
Bugs
Fixed in Version 8.30
Bugs
Fixed in Version 8.20h
Bugs
Fixed in Version 8.20g
|
|
|
New Features in 8.30
See The Magic Guide to What's New in Version 8 for a full
description of new features and functionality of Magic Version 8.30.
Magic Web Online (Top)
Magic Version 8.30 introduces a new and revolutionary solution for web
based application development, which enables the developer to create web
applications in the familiar online model rather than through a
batch-oriented approach.
Please refer to the supplied
documentation for a full description of the new Magic Web Online
functionality
HTML Merge (Top)
The Output Merge operation has been redesigned and now works through
the Output Form operation using an HTML Merge form.
When you
import a program from previous versions, the Output Merge operations are
translated to Output Form operations and the relevant parameters in the
I/O Properties dialog are transferred to new HTML Merge forms.
Magic Version 8.30 automatically trims trailing blanks in merge data of
updated tags. This is a change in behavior from previous versions. It is
possible to disable automatic trimming by setting the MergeTrim flag to No
in the Specials section of the Magic INI. The default setting is
MergeTrim=Y.
[MAGIC_SPECIALS] MergeTrim=N
New Wallpaper (Top)
Two INI settings, MDIClientImageFile and MDIClientImageStyle, were
added to the Environment section of the INI, which allows you to set a
background image to the Magic window. Please refer to The Magic Guide
to What's New in Version 8 for a complete description of these
settings.
Task Execution Repository Parameter
Description (Top)
The task execution window now displays the expanded description of the
parameters of operations, such as Expressions and Link Indexes. Whenever
the cursor is parked on such a parameter, its expanded description is
displayed at the bottom of the screen.
Flow Monitor in Background Mode (Top)
Magic Version 8.30 allows the developer to run the Magic Flow Monitor
while running a Magic Toolkit engine in background mode. This can be
done by setting LoadMonitor=Y in the [Specials] section of the Magic INI
file:
[MAGIC_SPECIALS] LoadMonitor=Y
Magic Broker added functionality (Top)
Broker Reload The Magic Broker INI file has a new option of
RELOAD=Y/N that instructs the Magic Broker to reload any registered Magic
server that was dismounted.
Broker Log The Broker log
file is now split upon creation to chunks of an average of 100,000
lines.
|
|
|
Additional Remarks: (Top)
AS/400 ISAM Transaction
In the supplied version of Magic for AS/400, when a transaction is
required for an ISAM table there is no longer a need to open the DB table
in the parent task. In each task where an ISAM transaction is required
the DB table can be defined and opened in that same
task.
CORBA Support Installation
The Corba support files are available for installation only on a
machine on which a Corba service is installed. The Corba support will
be available under the Middleware section of the Magic supported
components. The Corba support is still in BETA. A fully supported
product will be released by the end of July 1999.
License PAK
License PAK's for Magic
version 8.30 can not be processed by the license manager, which was
supplied up to Magic version 8.01. A license PAK of Magic version 8.30
can be entered only by a License Manager of Magic version 8.20 and
higher. License PAK's of all 8.01a and higher versions can be entered
in the supplied License Manager of Magic version 8.30
|
|
|
Bugs Fixed in Magic Version 8.30: (Top)
- Bug 970000 - JPG images were printed differently than they were
displayed in a 256 color setting.
- Bug 752402 - The memory allocation was not well cleared when using
the Direct SQL programs that are resident.
- Bug 698285 - The function VARPREV returned unexpected values when
evaluated in Create mode.
Now the evaluation of the VARPREV function
in Create mode returns the default value of the variable.
- Bug 291322 - A record locked in a subtask, which its ISAM DB was
opened in the parent task while using a Non unique index and the range
direction was set to be descending, the record was released only after
the parent task ended.
- Bug 688317 - To make Magic Version 8 more compatible with Microsoft
Windows standards, the control height values were changed.
To work
with the Version 7 control height default values, a new parameter has
been added to the Specials section of the Magic INI. [MAGIC_SPECIALS]
Def7EditHeight=Y
- Bug 341494 - A print preview IO, which was opened in a task and no
output operation was done, the window of the print preview was created
and loaded but not shown.
The bug was that the print preview window
was not removed at the end of the task, causing increasing memory
consumption.
- Bug 430310 - FILE2BLOB() function created corrupted BLOB data when
the native translation was effective.
- Bug 971521 - A 'Duplicated index: MVPhys' error occurred in creating
minor revisions when the native translation was effective.
- Bug 499508 - Hint was ignored when Link Join was performed.
- Bug 251945 - The Magic Broker crashed when it received an RQEXE
request with an empty name.
- Bug 243640 - The ADDDATE() function returned
'04/01/7908'date
when the result was a negative value of date. Now it returns a zero
value of date.
- Bug 764871 - The Magic Broker was also terminated when the RQRTTRM
was executed with 'entry number' 0 to terminate all server engines.
- Bug 9297 - An error that occurred in a subtask was automatically
aborted and not retried if the subtask was called from the parent’s task
suffix and the parent was ended with an 'Esc' key.
Was fixed using a
special flag: [MAGIC_SPECIALS] ClearCurrentAction=Y When this
flag is set, Magic will clear the current action every time a new task
is called.
- Bug 981389 - A resident subtask, which was called from a sibling non
resident subtask, using the events mechanism, caused the two subtasks to
overlap.
- Bug 427519 - Magic hanged when a subtask was called through an
event, while editing the content of an edit control which its default
value was of different size than the edit control in which the called
subtask was parked on.
- Bug 983556 - Linked record was not released after deleting the
record of the main table while the link is of the main table as well.
- Bug 753218 - Magic crashed when the caption of a window was
generated by an expression.
- Bug 980487 - The random function (RAND) produced negative values.
- Bug 751783 - A "Fetch out of sequence" error message was given when
running a batch program, which has a main table and a linked table and
one On Change level while the locking strategy was set to Immediate and
the transaction was set to 'On modify' in the record level.
- Bug 787351 - The last record after a range in ISAM was
updated/deleted by the ranging task if such a record was locked and
released during the range operatio.
- Bug 690345 - The first record outside a range in ISAM was fetched,
locked and not released if working with Magic locks.
- Bug 756879 - RQRESLST function - The minimum value of the range was
used also for the maximum value.
|
|
|
Bugs Fixed in Magic Version 8.20h: (Top)
- Bug 757738 - This bug occurred when importing a task from
Version 7 to Version 8 in which the Cache parameter in the DB File table
of a task was set to Yes and the Cache Size parameter in the File
Properties dialog was set to 0 or empty. The task was imported to Magic
Version 8, where the Cache Size parameter has been deleted. In this
case, the Cache setting remained Yes, enabling the cache, although in
the version 7 task, the cache was disabled by the Cache Size
setting.
This bug fix is relevant only when importing an application
from version 7 to version 8.20h. When doing so, the Cache setting for
those imported DB Tables with a Cache Size parameter set to 0 or empty
in version 7, will be set to No.
- Bug 996245 - In complex programs using the Memory Gateway, an error
number 43 was issued.
- Bug 759076 - In complex programs using the Memory gateway, Magic
displayed only one row in a Table control.
|
|
|
Bugs Fixed in version 8.20g: (Top)
- Bug 770894 - Magic running under Windows NT and using a generic
printer driver did not print a form feed character when such a character
was placed at the end of a text-based form sent as output to a printer
and its name was set by an expression.
This problem is fixed by
setting a new INI entry in the [MAGIC_ENV] section, GenericTextPrinting
= Y (Default: N). This flag is effective immediately. It can be set
to Yes using the INIPUT function before a task in which this situation
occurs and set back to No at the end of the task.
- Bug 978889 - Magic crashed to a memory leak. This occurred rarely
when outputting a text-based form.
- Bug 775180 - The Magic Broker did not support
SupervisorPassword longer than 30 characters. From Version 8.20g
the Magic Broker supports passwords up to 128 characters long.
- Bug 758384 - Magic had opened unnecessary cursors while using Range
using the MSSQL Database Gateway
|
|
|
Thank you,
The Magic Version 8 Team |
|
|
|
|
|
|
|