Ewan, a hint if u plz

If I remember correctly .. he used bitmaps 😃

Indeed Dazler is right.

The code creates the bitmap 'on the run' so there is nothing in the clock6.mbm file. Two elements (one vertical segment, one horizontal segment) are created.

There are then ten procedures that go...

PROC write_digit_0😞x_offset%)
REM draw digit zero
ENDP

and you call each one as required, telling it where to put the digit on the screen with x_offset%.

Is that enough to get you started?

Thanks. When i saw how "small" Digital35 font was, even with dbl height & bold, i was thinking of using mbm to load the needed 11 digits (0-9 and 😊 but thought i would ask you.

I'm dipping my toes into OPL as i got my 9210i 2 months ago. I'm not using NT and i don't have MS C++ so i think i'm confined to develop right on the phone (no emulator) - am i right in that?
I don't even have the "complete" documentation for the OPXs that are not on the help file (like AppFrame) but i'm guessing by reading some samples & looking at the "header" files (oph).

While starting to develop some apps, using the "core" as the basis, I decided to isolate the functionality of the application (any that would be written) from the services offered by the core.
So the event loop, the keyboard handler, the CBA handler and so on would reside in a fixed module.
This module can be compiled and loaded in each application, passing the needed inforamtion thru globals. The nice feature of OPL that greatly simplifies this task is the ability to call a procedure "indirectly" e.g. @(prco1$):, so if for example i want a special routine (MyProc) to do some complicated task when CBA1 is preseed, I can put it in the "core mudule" as:
@(G_CBA1_PROC$): and in the application module use the assignment:
G_CBA1_PROC$="MyProc" and coding MyProc in the application.

Anyways, thank you for the tip, and i hope i can post some more questions along the way. When i have some app ready, i will be happy to share it, if you are interested.

NBP

NBP,

Yep that'a a pretty good way to do it, and when the Series 60 core comes out, it will be easy for you to move to the new platform.

As to feedback here, looking forward to it!

On what platform will the new series 60 core run? why would it be easier?

on that digits theme: so for each segment (hor/ver) you do a series of gLine? I tried gPoly, pity one can't "fill" a drawn poligon, or can one?

10x
NBP

[quote="Anonymous"]On what platform will the new series 60 core run? why would it be easier?
[/quote]

It would be easier to port if you have (9210 events)+(app code) and want to end up with (Series60 events)+(app code)... rather than have (9210app) going to (Series60App).

on that digits theme: so for each segment (hor/ver) you do a series of gLine? I tried gPoly, pity one can't "fill" a drawn poligon, or can one?

Yep, a little batch of gLINES.

I have used the Nokia 9210i C++ SDK on Windows 98, without any problems. Also, without Visual C++ 6, just to install the OPL ER6 SDK.

Good luck,

Roberto

Roberto, that's good news. I will order the SDK cd-rom and try on my w98.
10x
NBP

you cna use something like patterns, I planned to look it up for you yesterday night but I didn't had the time.

Check the docs ... look for gbox, gfill and stuff ...

Dazler,
I thought about gFill, but the "beauty" of the LCD digits is that each segment is pointed at the ends. gPoly can draw them "hollow"

NBP

well if you still want a pattern then make black and white digits and gcopy them with an other pattern.

pattern + b&w image gcopy over eachother using mode 1 on the last

Info:
http://www.allaboutsymbian.com/develop/opl/opl3.php

You can have a full color image for the pattern, only the Black parts of the digit (which serves as mask) will display the pattern

I'm doing this out of my head, so this could all be wrong 😛