Calling the :setData() method of an XbpMLE object immediately after the
object was created may cause the application to hang up. The effects
of this anomaly depend on both the operating system platform as well
as on machine speed. On some systems, this anomaly does not occur at
all. The following factors have been reported to produce this problem:
o Operating system used is either Windows 2000 or Windows XP
o The application is deployed with accompanying manifest file (XP only)
o The computer used features a Pentium III CPU or better
This problem only occurs if the :setData() method is called directly
after object creation. Example:
...
oEdit := XbpMLE():new( oDlg:drawingArea,, {10, 10}, {270,150} )
oEdit:tabStop := TRUE
oEdit:create()
oEdit:setData( "This call may cause the application to freeze!" )
...
|
This problem seems to be due to an internal race condition, the
effects of which are made worse by fast CPUs. To work around this
problem, either try to call :setData() at a later point in your
code or try to add a call to Sleep() to delay execution.
A fix for this problem is available via Public Fix Level (PFL)
182306. Please visit www.alaska-software.com (support section)
for further information.
|