Wobbly scrolling – in progress

I’m still trying to fix the wobbly scrolling. There’s got to be some way of doing this simply.
Ok, I’m checking the keystate with the KeyCurrentState() call while scrolling, it seems to keep the animation in check.
I’ve just got the minor problem of flickering in the minimap now (high resolution).
Potential Fixes:

  • Don’t ever paint ‘under’ the minimap
  • Lose the minimap (not really an option)

Removing the paint-under for the minimap is an awkward one. For basic screen painting this requires preening the tiles that the minimap uses from the draw loop. The scrolling leads to an awkward problem. Previously the algorithm copied the entire screen up/down/left/right depending on the motion (memory prohibits a back-buffer).
In the interim, I’m allowing the toggling of the minimap in the configuration screen.

Minimap rendering correctly

Ok,
the rendering of the minimap correctly on scrolling works correctly. Now I have to fix the scrolling being sluggish.
The problem is that there is no key-up event on the palm.
Memory footprint has been reduced – I checked the code that was being generated and shrunk quite a few functions, and moved some functions to different sections as they were being called either once per execution, or very rarely. Not that anyone would really care about things like this except little old me.

Strange things on T3’s

That’s Palm Tungsten T3’s – Turns out that whatever way the version of pilrc I am using does the resources, it is screwing up the contents of the string lists. From what I can tell it looks to be an alignment problem with the strings.
I’ll get a later version of pilrc and try with that.

Power Consumption

It looks like the power consumption on 0.16 of Pocketcity is very high. I’m going to have to figure out why that is and work out how to reduce it. Someone complained about having used up 3/4 of their battery life after an hour, which is not good.
It’s an M130 and doing a quick google shows me that it should have a typical battery life of 4 hours.

Translations

I just received an offer to translate the Pocketcity into Catalan; which I appreciate. He’s mentioned that he’d like to have the .po files which tells me that I’m probably doing the translation of the application all wrong.
Currently I’m using the lang attribute of the .rcp files to split up all the separate languages that are used, and I realize that I could miss strings using this method. I have found that during testing I have missed strings so the ould is a bit of a misnomer.

Time for a wee bit of math (minimap)

Ok,
We have the X position:
– getMapXPos()
this is a fraction of the overall display:
(getMapXPos() / getMapWidth())
multiply by the width of the display.
Making sure to order them such that there is never a zero value
for the multiplication.

More palm5/6 woes

the high resolution support for the PalmOS5 is driving me nuts.
little new pieces of the API seem to appear every now and again that make older code stop working. The testing matrix looks like:

  • pre palmos 3.5 device
  • palmos 3.5 device
    • grey
    • color
  • palmos 4 device
    • grey
    • color
  • palmos 5 device (simulator)
    • 320×320 resolution
  • palmos 5.?? device (simulator)
    • collapsible display, reorientable display
    • 1, 1.5 and 2x resolution
  • palmos 6 device (simulator)
    • all the 5.?? matrix

It’s quite a trek to make sure that it works in all the devices. I need to codify the testing matrix.

Need to change the distribution algorithm

The distribution algorithm results in some silly output. There are times
where zones that are adjacent to power plants have no power.
I need to flag power shortages as well.
It looks like wasps find me sweet…