new minor release

version for wm 6.5.5? i have a htc touch with rom Onyx 6 with wm 6.5.5 and it not work

Which one is the new version? uTask_1_4_170611.cab
I still have the problem with the double tap to get out of tmail.exe

Random problem - Start Menu does not start

---

Hi Ultrashot,
I've been using the march version of uTask, and found a weird problem when using Notification enhancement and Menu enhacement from the latest Oboe 1.18.
Ramdonly after fresh flashing or hard reset, the start menu does not start and them manila does not start.

Do you cook these Oboe packages in your ROM?
have you seen a similar problem?

EDIT:
Not related to Utask.
Thanks for your good work

Originally Posted by ypsmav

Hi Ultrashot,
I've been using the march version of uTask, and found a weird problem when using Notification enhancement and Menu enhacement from the latest Oboe 1.18.
Ramdonly after fresh flashing or hard reset, the start menu does not start and them manila does not start.

Do you cook these Oboe packages in your ROM?
have you seen a similar problem?

I'll be cooking with the new version now, and I'll disable the hook on the time and see if the problem is solved.
Thansk

I don't like oboe packages, so I don't use them. No such problems on my packages.
btw, N.E. and M.E. aren't responsible for start menu and manila anyhow.

Have seen Utask 1.5 is released for your wm rom.
Does it goes to public?

Dear Ultrashot,

I'd like to ask you for a brief explanation.
For the past 6 months I use Jackos Rhodium EVO ROMs (earlier on build 28236 and now on 21690). They have uTask cooked in from the beginning and I love this tool. I always configure the "cross softkey" for Close instead of Minimize.
But for several months I have a minor problem with applications not being able to store their settings when closed using Close softkey.

The example here are CorePlayer, MobiPocket, Word or AdobeReader. The CorePlayer and MobiPocket have their own Close functions in their menu, and when I use the "built-in" Close function they close and store the settings. But when I use Close softkey they are closing but no settings are stored.
Since Word and Adobe don't have any other Close function I have to set their preferences every time I start them.

But I'm almost sure that it did not work this way at the beginning. This is a minor issue so I didn't dig up as well, but today a guy from Polish forum has drawn my attention to the difference between uTask closing and built-in closing.

Can you comment on this? Does the "Close" action from uTask really closes application or just kills the application process?

Originally Posted by Skrobel

Dear Ultrashot,

I'd like to ask you for a brief explanation.
For the past 6 months I use Jackos Rhodium EVO ROMs (earlier on build 28236 and now on 21690). They have uTask cooked in from the beginning and I love this tool. I always configure the "cross softkey" for Close instead of Minimize.
But for several months I have a minor problem with applications not being able to store their settings when closed using Close softkey.

The example here are CorePlayer, MobiPocket, Word or AdobeReader. The CorePlayer and MobiPocket have their own Close functions in their menu, and when I use the "built-in" Close function they close and store the settings. But when I use Close softkey they are closing but no settings are stored.
Since Word and Adobe don't have any other Close function I have to set their preferences every time I start them.

But I'm almost sure that it did not work this way at the beginning. This is a minor issue so I didn't dig up as well, but today a guy from Polish forum has drawn my attention to the difference between uTask closing and built-in closing.

Can you comment on this? Does the "Close" action from uTask really closes application or just kills the application process?

u task is just quick linking to the phone's default task manager and the default phone task manager probably by Microsoft was made way before all those their party apps like coreplayer and adobe for windows mobile thus they of course programmed it to kill or force close these apps as it does not have knowledge in telling each apps in each way to close and save settings... well Microsoft surely didn't have time to make more new Roms as new third party apps arrived just to let the default task manager tell those apps to close and save settings nicely...

Hello,
Thanks for explaining.

But one thing is still unclear for me.
If I use the same third party apps under WM6.5 environment, they always save the settings when closed with the "X" in upper right corner, which is - afaik - the native function of Windows Task Manager.

If uTask function is just calling Task Manager to close an application, then it should behave in similar way, don't you think? That is why I asked for explanation.

UPD:
I made some experimenting.
uTask 1.3 and 1.4 work well. They trigger closing apps. The problem is only with uTask included in Jackos ROMs. I can see by the version of dlls that this is different than the ones in 1.4. And the behaviour is different there. Perhaps this is just a matter of settings?