[JAMin, XDA Neo, S200 General] ikarus:
thanks for reporting.

you should add extend="10" to your sliding-View, but there is still an issue then.. i don't know if that can be solved while keeping the performance.

I'll have a look into that.

thanks for your work on the diagramm ;)

It shows the problem pretty good.

Of course it can be calculated, but on what cost?

You have to check for any Item the bounding box for image/imagealt/label and adapt the extend. One calculation has to consider the position of each bounding box and there are more calculations as well.

what i want to say is: i haven't found an algorithm that runs in linear time and that's important for scaleability, e.g. for big xml-files respectively complex themes.

Just compare following: Let the cpu spend much time and stack usage on such calculations or just add an extend-attribute? What would you want as a regular user?

Keep in mind that your pda/phone is not a desktop-computer! It's not a computer with 1GHz-Cpu and has not 2GB-Memory! It's more an embedded device and an application developer or theme-maker should know about the needs of that!

I guess here you can see the difference between software for desktop-computer with software, that takes care of the needs of embedded systems.

I'll check the code for automatic calculation of extend again, but i'm almost sure that it's too inefficient for such a small device.

Yes, you're right hehe

This is an artificial limitation, due to my experience regarding usability and affordances.

Don't think as a developer or a theme-maker, but as a user with ad-hoc experience with mobile devices.

If you tap and hold on an Item, then

-> what would you expect?

-> respectively why should you tap and hold on that Item?

If you have an advanced-menu, then why not spend it a button and make it clearly visible that there is more..?

If there are really good reasons or this discussion leads to some insights (which i don't know yet) then it's not a problem to allow this :D

i agree as a developer hehe

but considering the big picture.. i do see it different

that's a "great bug" hehe..

thanks a lot for reporting!!

Now i know the conditions for this crash. It'll be fixed with next build!

great :D

yes. It should work with any today-plugin, but Spb Diary does a lot of things different, so i don't give an OK for Spb Diary.

yes, it'll be available with 1.07 (near January 2009)

There are a lot of performance things to solve for advanced landscape-support.

i could add an placebo-thing for estimation of remaining battery lifetime, but it's .. hm.. hehe.. be honest.. which one of the estimation apps gives you a realistic estimate?

I thought several times about such an estimate, but it is never an appropriate estimate and it's just code that does "something", but not really useful. Am i wrong?

If there is really such an placebo-thing needed, then ok.. i don't mind add it, but it's really only code that does "something" hehe

At least my device-usage-profile is so much dynamic, that it's so much different for each day. An adaptive-value can't cope with that usage.

Let me know if i'm wrong.

I'll check that, but i guess it has to do with getting a "Screenshot" from the today-plugin.

it's the background you've specified with your xml.

If you don't want to have it, then add cachebg="0" to the tPlug-Item. It should be in the manual, but don't know for sure.

If it doesn't work either, then add animatebg="0xFF000000" to the Window-Tag as well.

It looks like you have a new device ;)