Recent changes to bugs

OPL DevPack error

Anonymous — Mon, 28 Jul 2008 09:59:35 -0000

The OPL devpack 2006-06-17 (full with PC support) ZIP file is ruined, my Linux system gives me this error when trying to open the file:

[/tmp/9200-OPL-DevPack-2006-06-17.zip]
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
zipinfo: cannot find zipfile directory in one of /tmp/9200-OPL-DevPack-2006-06-17.zip or
/tmp/9200-OPL-DevPack-2006-06-17.zip.zip, and cannot find /tmp/9200-OPL-DevPack-2006-06-17.zip.ZIP, period.

On Windows XP even WinRAR can't extract the files but shows the archive's contents.

Problem running Fit4Life

Anonymous — Tue, 03 Apr 2007 09:32:16 -0000

I installed Fit4Life when I bought my P910i in 2005. I
was able to run the program Fit4Life in my P910i then.
However, I saw the program in Steve Litchfield website and I uninstalled my existing Fit4Life and installed the one found in his website thinking it was more original
since it came from the creator of Fit4Life.

It was during that time that I can no longer use the
jog dial to get the pulse reading , and the error
message occurs everything I use the jogdial ""Application cannot be started".

I can still run the program but somehow I cannot use the jog dial to get the pulse reading. Steve Litchfield said it could be problem with the runtime. Hope you will be able to find the solution to this problem. Good luck. Cheers.

Alarm setting -> fatal crash of phone

Anonymous — Tue, 25 Jul 2006 15:23:42 -0000

Using the function AlmSetClockAlarm (Alarm.opx) causes
a fatal crsh of the phone so a hard reset is
necessary. I use the new version 1.56.

The function worked fine with EPOC 5.

I changed the anAlarmNumber& and the aSound$
parameters several times, but it does not help.

Anybody an working example for me?

Regards
Klaus

Runtime with active menu freezes when focus switches

Arjen Broeze — Fri, 16 Jun 2006 04:24:04 -0000

The runtime "freezes" when the focus is switched away
from an OPL application with an active menu (for
example by using a hotkey or by pressing one of the
application buttons on the Communicator).

Although the OS closes the menu, the runtime still
thinks the menu is displayed. Since the code is
waiting for the menu to close using the active
scheduler, no updates take place on the screen, making
the application appear frozen.

If one of the CBA buttons is pressed on the
Communicator (which also uses the active schedule) the
OPL application will crash.

The solution is to press the menu (which cancels the
open menu and creates a new one) and then cancel that
menu. This restores the application's functionality.

PEEK$ sometimes doesn't work

Arjen Broeze — Mon, 05 Jun 2006 08:29:11 -0000

PEEK$ sometimes works and sometimes causes unexpected
results (KERN-EXEC 3, "No system memory" errors).

The reason is that POKE$ doesn't clear the 2nd byte of
memory (the byte directly after the string length
byte). If this byte happens to be zero (which is
usually is at the start of a program) PEEK$ works
correctly. If it is not, PEEK$ will cause the above
mentioned errors.

This is fixed in runtime version 1.55

LOC partially broken

Arjen Broeze — Fri, 02 Jun 2006 00:05:03 -0000

The LOC function doesn't work when searching for a
string that contains an embedded CHR$(0).

The following example

PRINT LOC("ABC"+CHR$(0)+"DEF",CHR$(0))

will print 1, instead of 3.

This is due to a bug in Symbian. LOC internally uses
FindC() and apparently the CHR$(0) get "collapsed"
into an empty string which is then found at the first
position.

Runtime crashes with "Does not exist" or "Font not loaded"

Arjen Broeze — Wed, 24 May 2006 01:23:38 -0000

When the first started OPL application is terminated,
it unloads the default font (EON14.GDR) making it
unavailable for other running applications, which
eventually will crash with a "Does not exist" or "Font
not loaded" error message when these programs attempt
to create a window, load or create a bitmap or set one
of the standard fonts.

The reason is that the OPL runtime only loads the
default font at startup if it is not already present
in memory. If the font is loaded by the runtime, it is
unloaded when the runtime exits.

Typical scenario:
OPL application 1 starts - EON14.GDR is loaded into
memory
OPL application 2 starts - EON14.GDR is not loaded
again
OPL application 1 ends - EON14.GDR is unloaded from
memory
OPL application 2 uses gCREATE, gCREATEBIT, gLOADBIT,
gFONT or gSTYLE - crash

The solution is to always load the font in the runtime
regardless whether it is loaded or not.

CBA keys sometimes don't display correctly in OPL dialogs

Arjen Broeze — Fri, 13 Jan 2006 08:19:27 -0000

Sometimes portions of the screen are shown in the CBA-
area when an OPL-dialog is shown on the screen.

Example to reproduce the problem:

DO
dinit " ",19
dbuttons "again",%a,"quit",%q
dposition 1,1
d%=dialog
UNTIL d%<>%a

If you keep pressing the "again" button (at least 10
times) the phenomenon will show. Using
SySendKeyEventToApp to shift the focus in the dialog
to another control than the first one is also almost
guaranteed to reproduce the problem.

Declaration errors in System.oxh

Arjen Broeze — Fri, 13 Jan 2006 07:58:07 -0000

The functions SySetForegroundByThread and
SySetBackgroundByThread are incorrectly declared as
functions with a float return value. These functions
return a longint.

The current declaration is:
SySetForegroundByThread:(threadId&,previous&) :38
SySetBackgroundByThread:(threadId&,previous&) :39

The correct declarations are:
SySetForegroundByThread&:(threadId&,previous&) :38
SySetBackgroundByThread&:(threadId&,previous&) :39

Status field not updated correctly

Arjen Broeze — Fri, 23 Sep 2005 03:47:58 -0000

When an OPL program uses AppFrame.opx on a
9300/9500, the status bar is not correctly updated (only
the top part is being drawn). This becomes visible when
an OPL application that uses the full width status field is
started from an application that has a small statusfield
or no statusfield at all (for example when running an
application from the OPL editor in fullscreen mode).