Large clock on 3310?

[ShadoW2004]

Is it posible to make clock on 3310 Large/Bold font on main screen?

I wont to make 3310 screen like on Nokia Symbian phones (like Nokia N70)

We can play with zones...

[yak]

You will probably have to change two things. The upper status bar zone size and one of the windows tags (to change the font used for the clock, see dump_windows_tags.nrx script for NokiX). Changing the zone will probably force you to adjust other zones making them too small for some applications so I don't think this is a good idea. But I may be wrong...

[ShadoW2004]

Thank you Yak! I will try to play with dump_windows_tags.nrx...

[ShadoW2004]

Ok, I have somethink like:

@attr id=0x1 flags=0xFF wflags=0x0 enable=0x1 tag=<ALCH><ALB><FS2><TR1>

@attr id=0x2 flags=0xFF wflags=0x0 enable=0x1 tag=<ALR><ALB><FS2><TR1>

@attr id=0x3 flags=0xFF wflags=0x0 enable=0xFF tag=<FS1><TJR><ALB><ML2><MR1>

@attr id=0x4 flags=0xFF wflags=0x0 enable=0xFF tag=<AR><FS1>

@attr id=0x5 flags=0xFF wflags=0x0 enable=0xFF tag=<ML3><ALR>

@attr id=0x6 flags=0xFF wflags=0x0 enable=0xFF tag=<MR2><ML3><ALR>

@attr id=0x7 flags=0x10 wflags=0x0 enable=0xFF tag=<FS2><TLH12>

BUT how to find clocks @attr id?

[yak]

That's the problem with tags. There is no easy way to determine what part of the user interface are they describing .

In general, it is good to take a look at the dump_windows.nrx script (distributed only in package with script sources). It displays a list of all "windows". A window is defined by a zone, drawing routine, attr ID and some flags. In this listing you can spot some relationships between zones and atrributes (AKA window tags).

However, there is more attributes than windows. This is beacause FW changes the attributes of windows at run time, it can also divide a window in some sub-windows and assign different attributes (tags) to them. This complicates things a bit.

The upper status bar is such case. It is a single window (using zone [0,0,84,7]) which is being divided into sub-windows (possibly with different tags) at run-time.

So, in this case there are only two ways to find the right attribute ID. You can analyze the status bar code in WinARM but that's very hard.

What you should do is to locate all attributes with <FS3> tag. This tag selects the "tiny/plain" font which is originaly used to draw the clock. Then you have to start changing this tag to (for example) <FS4> which will select "ftest/plain" font (net monitor font). This should be safe beacause ftest font is small enough to fit into the status bar zone without changing it. So, when the clock font will change, you got it.

Cheers,
[Yak]

[ShadoW2004]

I found only one @attr with <FS3> tag:

@attr id=0x71 flags=0xFF wflags=0x0 enable=0xFF tag=<FS3><ALB><ML1><MB2><B1>

and changed it to:

@attr id=0x71 flags=0xFF wflags=0x0 enable=0xFF tag=<FS0><ALB><ML1><MB2><B1>

BUT clocks not changed font type!

[yak]

Damn, I thought that this is done as all other things in Nokia's user interface. Now I've actualy checked this and saw that it's made somewhat different.

You will have to play in HEX of create yourself a script to make it work.

I will use 3310, v6.33 as an example:

At address 0x237b90 (subtract 0x200000 to get a flash file offset) you will find two addresses. First point to "tiny" string found in fonts table, second points to "plain". This is the font used by upper status bar. Changing these pointers will most likely do the trick but will cause all the status fields to use the new font, this includes the net monitor page number for example.

The "large" and "bold" strings are placed near the other ones in the same fonts table. "large" is at 0x310bcc, "bold" at 0x310bd8.

I haven't tryed this but to my best knowledge this should change the font.

Best,
[Yak]