I assume that everybody's aware of the possibility of and ensuing problems with custom menus (certain menu items no longer being available).
A clever solution to this problem, called
MenuTT, was published on
tomtomheaven. MenuTT allows you to switch between your custom menu and the original one. Problem solved, very practical. A detailed explanation on how to use it can be found
here.
But:
There's several things I dislike about the way that MenuTT works:
- The programs in SDKRegistry are removed from the original menu. Now there may be a good reason for that. I'm not sure, but from reading this and other forums, it appears that having anything in SDKRegistry or the use of a custom menu has different effects on the various TomTom models. With my -- rather brand new TomTom GO 730 T -- whatever is in SDKRegistry gets tacked on to the original menu without problem. It's just that I can't put certain menu items into a custom menu. So, no need to remove them.
- Switching back to the custom menu requires going to 'Browse map' and then clicking on some sub-option. Again, this clumsiness may be due to what happens on other TomToms. No need for that on mine. All I need is an extra 'program' in SDKRgistry.
- At one point MenuTT managed to crash the TomTom. When, afterwards, I connected it to my PC, I found that my entire SDKRegistry folder had been wiped out, and when I tried to write back the contents, WinXP also crashed. I had been listening to a music file when I invoked MenuTT, which was probably not such a good idea, but, anyway, I'm not really comfortable with MenuTT's messing with my SDKRegistry folder.
The way I figure it, all you really have to do is rename TomTom.mnu (e.g. as Tom.mnu) and then restart the nav application. So, here's my alternative way of doing it.
Caveats:
MenuTT takes care of some files called ttn and cleanup.txt, which I don't have or use -- my version doesn't. So, if you do use these files, then you'd probably want to adapt the .sh-file accordingly.
As with MenuTT a restart of the TomTom navigation application is required. This takes a few long seconds, and if you're currently navigating a route, you'll lose that.
Download the attached SwitchMenu.zip and unzip it to the root of your TomTom. Files are:
bin/switchmenu.sh
sdkregistry/SwitchMenu.bmp
sdkregistry/SwitchMenu.cap
---------------------------------------------------------------------------------------------
I also assume that everybody's aware of the various ways in which screen dumps can be produced. The simplest way is to create a folder 'screen' and put an empty file 'capture' in there. Then, whenever you tap the top left corner of your screen, a screen shot is dumped into a file 'dump<nnn>.bmp' in that folder.
Nifty, but this can sometimes be a problem when you want/need to use the (-)zoom function e.g., or you may hit the corner inadvertently thus creating lots of pointless dump files.
Again, the solution consists simply of renaming a file and restarting the nav app. Here we flip between 'capture' and 'no-capture'.
Download the attached Screendump.zip and unzip it to the root of your TomTom. Files are:
bin/screendump.sh
sdkregistry/Screendump.bmp
sdkregistry/Screendump.cap
---------------------------------------------------------------------------------------------
When you look at the *.sh files you'll see that I kill any possible mplayer processes as well as ttn, just to be on the safe side.
Enjoy!