[Windows Mobile Apps and Games] MichelDiamond:
Hey mate,

thanx for asking so kind.

Unfortunately I can only quote, what I've said, as I posted the fix:

To make it a little bit more transparent:

Co0kie and me have a development for CHT as a "shared development" - so everybody has his parts.

My parts are the system parts of CHT - I'm responsible for almost all state indicators (battery, RAM,...) and much of the functional toggles. Also for event handling like e.g. that device is (timeouted) locked because of an action and such things. All my parts for CHT are written in fast C and they are used by Manila to show it, they are configured by CHTEditor and they can be notified by CHT (and the toggles - so by the user).

Co0kies does the main part - the LUA development of Manila and all the nice things, you appreciate of CHT's Layout flexibility.

Our interface is the event/notification-level of WinMo and the Registry.

So I can update my part sometimes independent of him, but usually my parts are simply in CHT-cab inside. In this case I made an exception and posted it here earlier, because of the tests.

It was to see, that I can counteract some of the major issues by chtstate. The problem is, that manila isn't used to so much updates for quicklinks and so the manila drains sometimes the battery to update. But that's manila and almost not to change. But chtstate can make it - I added some user idle detections, got help from the CHTS beta group with much log-files to see, what happens, created new more intelligent timeout and added notifications because of this experiences and so chtstate got some new versions - and now it's the internal version number 1.08f.

Usually you don't see this number as user - and if you are interested - in CHT 2 public beta the version of chtstate is 1.00rc4

So if I post a fix for CHT then you can be asure, that it's a common update for CHT - but like said: Usually it's in CHT .cab and so you can't mention it.

And that could also answer a little bit your question: Co0kie has also much to do in RealLife and only he can say, when CHT 2 final will come. That's not my decision.

I wanted also to reduce the useless "F5"- or "countdown"-postings here - that all costs time (and nerves) for us to read and also it's only confusing for everybody, who searches for help in this thread. We need reports of issues here, or reports what's working (both with version infos) or simple Thank you's, which motivates somebody to make free apps for the community. To be pressed is the opposite of it - and I really thought about suggesting to postpone the final release for each 1 day for each such a "pressure post" :)

But the main aim, why I posted an update, is, that I know, that it helps all CHT v2-users and Co0kie has now more time until he can release it. And our team to check and/or improve it.

So simply consider chtstate108f as beta-final Release of CHT - as far as Co0kie will tell you, when he will come up with CHT v2 Release.

Please respect especially Co0kie's big effort and also that nobody of our team wants to release a half-baked CHT v2 final.

I think with chtstate-update your CHT v2 works quite fine and the other things will come, as soon as Co0kie can tell it to you. Issues are not good planable. And also the need of time for important private things in Real-Life.

I hope it's a little bit more transparent, why you've got an update with such a strange number - so it's easier to wait. Please desist of asking when it will come until Co0kie announces it official without the word "expect" :)

Thanx for reading - and I'm really happy, that you all are happy with chtstate108f for this while.

Regards

Micha