QMediaLight 1.2.6 ReadMe
© 1998-2004, Escape Information Services -- All rights
reserved.
Contact information
Technical support
Please visit our support pages for an overview of Escape Support and FAQs:
http://www.escape.gr/q/support/
When submitting a support request, please provide as much information as
you can concerning the computing environment, platform, memory
settings, other plug-ins, versions of OS, plug-ins, 4D, error
codes returned by our products, as well as any other details that might
help us reproduce whatever causes you trouble.
System Requirements
QMediaLight 1.2.x is available in 3 different platform versions:
Plug-in version |
Plug-in files |
Use with 4D |
System requirements |
QuickTime |
|
In Mac4DX:
QMediaLight.4DX |
4D 6.06 - 6.7x |
MacOS 8.6 or later |
v5 or later
|
|
In Mac4DX:
QMediaLight.4CX |
4D 6.8x |
Same as 4D 6.8x |
|
In Win4DX:
QMediaLight.4DX
QMediaLight.RSR
QTMLGlue.DLL
|
4D 6.06 or later |
Windows 98/NT4 or later |
Note: If your database uses more Escape plug-ins, please make sure that you
use the right versions. Versions you should use with QMediaLight 1.2.x are:
What's new in QMediaLight 1.2.6
Bug fixes:
- 4D 2003.2 changed the way it draws plug-in areas and this caused
update problems in the movie plug-in area. Fixed.
- Identified and corrected a potential issue where the developer license would
not be copied to the compiled structure when building
compiled or standalone applications with 4D 2003.x.
- Restored compatibility with Win NT/SP6a.
- Long path names are now supported on Win NT.
- It was possible to crash on 4D Server when a client was logging out
if at that time the licenses dialog was open. Fixed.
Known issues:
- The QTVR problem is still there (see "Known issues" below). 4D
egnineers are still aware of the issue, but no fix has been released as
of 4D 2003.2.
What's new in QMediaLight 1.2.5
Bug fixes:
- It was not possible to open movies that had their movie atom stored
in the resource fork instead of the data fork. Fixed.
- Fixed a bug where the plug-in could crash after switching to another data
file with OPEN DATAFILE or CREATE DATAFILE. MacOS X only.
- Under rare circumstances the plug-in could fail to load expansion
licenses on Windows. Fixed.
Known issues:
- The QTVR problem is still there (see "Known issues" below). 4D
egnineers are still aware of the issue, but no fix has been released as
of 4D 2003.1.
What's new in QMediaLight 1.2.4
Bug fixes:
- QM_Play(areaRef;0) would not stop a playing movie. Fixed.
- QM_GetSelection would always return error 1. Fixed.
- On MacOS X QMediaLight would fail to resolve a pathname if the name of the disk contained a
slash character ("/"). Fixed.
- In a rare case licenses installed when running under 4D Server
would not be saved. Fixed.
- Under certain circumstances QMediaLight could cause long delays during
application startup. Fixed.
Known issues:
- The QTVR problem is still there (see "Known issues" below). 4D
egnineers are still aware of the issue, but no fix has been released as
of 6.8.3.
What's new in QMediaLight 1.2.3
Bug fixes:
- When running under 4D Server on MacOS X an error dialog reporting
"no stack memory" would pop up continuously. Fixed.
- Under certain circumstances it was possible to loose installed licenses
when running under 4D Server on Windows. Fixed.
- Under certain circumstances the file selection dialog would not accept
mouse clicks when running the PPC version of the plug-in on MacOS 9. Fixed.
Known issues:
- The QTVR problem is still there (see "Known issues" below). 4D
egnineers are still aware of the issue, but no fix has been released as
of 6.8.3.
What's new in QMediaLight 1.2.2
Bug fixes:
- There were errors in the documentation for the QM_TestMovieFile command.
The command docs have been updated to correct these errors.
- When using the classic PPC version of the plug-in with 4D 6.8.x
under Mac OS 8/9, there were problems with movie display in the plug-in
area. Fixed. Mac only.
- When calling a plug-in command on Windows without QT installed,
QMediaLight might crash due to a bad check for QuickTime's presence. Fixed.
Win only.
- The product name returned by the QM_GetVersion command now shows
whether the plugin is Carbon-based or not. For example, the Carbon
version of the plug-in will return "[plug-in name] [version] Carbon",
and the corresponding PPC version will return "[plug-in name] [version]
PPC". Mac only.
- On some localized systems (Russian, Japanese) 4D would present a
syntax error dialog during plug-in initialization and the plug-in would
fail to display the license registration dialogs. Fixed. Mac/Win.
- If 4D Client attempted to call a plug-in command when no license
seats were available on the server, the plug-in would block program
execution instead of faling back into demo mode. This is now fixed; the
plug-in will run in demo mode as expected. Mac/Win.
Known issues:
- The QTVR problem is still there (see "Known issues" below). 4D
egnineers are still aware of the issue, but no fix has been released as
of 6.8.3.
What's new in QMediaLight 1.2.1
Bug fixes:
- Fixed a potential crash during startup when running with 4D 6.7.x.
- Fixed a bug that could cause long delays during startup when
running with 4D Client on Windows.
- Fixed a problem where the "Escape" menu would become unresponsive
when running with 4D Server 6.8.x on Windows.
Known issues:
- After much investigation we have identified the cause of the QTVR
problem (see "Known issues" below). The problem is not in QMediaLight
or QuickTime, but in 4D. The egnineers at 4D are aware of the issue,
and hopefully there will be a fix in a future update of 4D 6.8.x.
What's new in QMediaLight 1.2
New features:
- Carbon version runs natively on MacOSX
- Revamped import/export dialogs using Navigation Services on
MacOSX/MacOS
- New license control system
Known issues:
- There is currently a problem playing QuickTime VR movies under
MacOS X. QuickTime complains that memory is low and displays a broken
movie icon. This does not seem to be a QMediaLight issue (we have
reproduced the problem outside QMediaLight). It seems to be some
obscure anomaly or incompatibility between QuickTime and 4D. We will
keep investigating this issue; as soon as we come up with a workaround
or fix, we will release an update.