Harr, guess what - it wasn't a cold, and it's not over yet. Instead I decided to grow a nice little kidney stone, just for the fun of it...

But, looking at the bright side, couldn't sleep thanks to the pain, so at least I updated ApMeFo to distract myself from that little kidney bastard.

As promised, the main change in this build was the addition of a little diagnosis tool to help with getting rid of those unknown problems some of you are still experiencing.

So, everybody who can't seem to get ApMeFo to work, please select "Diagnosis Tool" from the menu bar, hit "Copy to Clipboard" and paste the result here in this thread.

So far it

• Checks whether hildon.menu exists (=ApMeFo has been activated)
• Checks whether hildon.menu differs from the ApMeFo standard .menu file (=has been modified by hand/another application)
• Displays the modified hildon.menu in case they differ
• Displays a list of all .directory files
• Displays a list of all .menu files

This should make checking for possible reasons a bit easier to both you and me.

Other than that, there's been a few additional changes:

• By request I moved the Readme (which is still rather empty, anyway ) to the menu bar.
• Made the (De-)Activate the first tab, for two reasons: With the Readme gone, this tab now resumed the task of displaying the warnings on the front page. Also, now clicking the Activate button is the first thing to do, so now it should be more intuitive to activate in order to make ApMeFo work.
• Made the link in the warning window click-able. It now opens the post in a new browser window.

Tomorrow I'll try to come back to the various questions not answered yet and to sum up the suggestions and requests given on the last two pages (thanks a lot to everybody).

Well, provided my pain killers decide to kick in.