|
Version 6.0 (for the TomTom GO) Additional Configuration Options
1. Introduction Several default configuration components of the TomTom GO can be adjusted, allowing users to modify the appearance of the TomTom GO. By creating certain files to be placed on the SD card, the splash screen that is shown when switching on the TomTom GO can contain a picture of your choice, the appearance of the menu can be modified and the list of colour schemes can be extended with user-defined colour schemes. This section explains how to replace the splash screen, how to define a customized menu and how to add a colour scheme. 2. How to add a splash screen The Splash Screen of the TomTom GO, which is the window that welcomes the user when switching on the device, can contain a picture of your choice. By placing your own bitmap in the right place on the SD card, your picture will be displayed when turning on or off the TomTom GO. There are two different types of splash screen. One type for devices with a non-widescreen display, called splash.bmp, and one type for widescreen displays, called splashw.bmp. 2.1. Example splash screen This is an example splash screen for non-widescreen devices. Warning: The file 'splash.bmp' could already be available in the root of the SD card. If so, make a copy of that file before completing this example. Copy the file called 'splash.bmp' from the /TomTomGO-SDK/examples/additional_configuration/ folder to the root of the SD card. Turn the TomTom GO off and then on again. The splash screen will briefly show when turning the device on. 2.2. Adding a splash screen When you want your own splash screen being displayed when turning on or off the TomTom GO, create a bitmap with the following attributes: For non-widescreen devices:
It will be rotated -90 degrees when shown on the TomTom GO, so make sure you rotate it 90 degrees clockwise before you transfer it(the left-hand side of the bitmap will become the bottom of the Splash Screen). For widescreen devices:
It will not be rotated, like splash.bmp. After the bitmap has been created, copy it to the root of the SD card. When switching on the TomTom GO, it searches for a file called 'splash.bmp' or 'splashw.bmp', depending on the type of device, in the root of the SD card. If available and correct, the picture will be displayed in 65536 colours. 3. How to customize the menu The way the menu items on the TomTom GO menu are arranged can be modified by defining your own menu. Furthermore, items can be deleted, default icons and descriptions can be replaced by user-defined ones and items can be greyed out. A customized menu for the TomTom GO is defined in a text file, which is read at start-up. If available and correct, the menu defined in this file will show instead of the default menu. Don’t worry if your menu is not what you expected, just delete or rename it and the TomTom GO default menu will show again. 3.1. Example customized menu Copy the following text into a file called 'TomTom.mnu' or use the corresponding file from the /TomTomGO-SDK/examples/additional_configuration/ folder. Don’t worry if your menu is not what you expected, just delete or rename it and the TomTom Navigator default menu will show again. 3.2. Example customized menu Copy the following text into a file called 'TomTom.mnu' or use the corresponding file from the \TomTomPPC-SDK\examples\additional_configuration\ folder.
Put the file in the directory SdkRegistry/ from the root of the SD card. The full path to this directory is /mnt/sdcard/SdkRegistry/ Also, make sure at least one of the previously defined capability files is available in /mnt/sdcard/SdkRegistry/. The command defined in the capability file will now show as the 5th menu item of the first main menu as defined by "MENUITEM|TASK_SDK1|". If you do not have a capability file available and you still want to complete the example, just remove that line from the 'TomTom.mnu' file. If the connection with the SD card is made through HyperTerminal, the command 'sync' should be given at the terminal to force the changes to the disk. Now reboot the TomTom GO and browse through the main menu. The TomTom GO will now show a custom menu. 3.3. Defining the menu To define a menu, a text file should be created with the following name:
In this file the menu items to be shown on each page of the menu are defined. The format of the TomTom.mnu file is pipe-separated ASCII, where each line consists of at least a level and one of the predefined names defined for that level. Three levels can be distinguished:
To define a menu, you first have to define the menu block:
where
Every line after this will be interpreted as a page or an item of the main menu. Then a page is defined, by:
where
Now, the menu items are defined for each page. The first item of the first page of the main menu is the predefined menu item "Advanced Planning":
The second item of the menu says "Go Somewhere" and selecting it brings you to the default "Navigate To"-functionality:
The description “Navigate to...” has been replaced with “Go somewhere”, the icon is the default TomTom GO icon. The next menu item in the example is the predefined “Find Alternative”. In this case the icon for the menu option has been replaced by a user-defined icon and the description has been replaced by "Alternatives...":
To use your own bitmaps, place your .BMP file in the /TomTom/SdkRegistry/ folder on your Pocket PC. If the bitmap isn't available, the default icon will be displayed. To browse through the menu, one of the 6 menu items of each page should be reserved for the next-screen item:
This shows the default arrow for going to the next page and selecting it from the menu will bring you to the next page. Finally, an icon can be greyed out by adding 1 as a final argument:
The menu option “My Phone” will show on the menu, but it is greyed out and can not be accessed. Please note that the pages are interpreted in the order in which they are defined and not by the number of the TASK_PAGE, so make sure the pages are defined in following order. For an overview of the predefined menu items, see :
A special item TASK_SDKn is defined:
This item represents the command to be sent to an external application, as defined in a capability file. If you have several commands to send or several applications to start, you should define a different TASK_SDKn for each command. If you have three commands defined in capability files, these items should be defined in the menu: TASK_SDK1, TASK_SDK2, TASK_SDK3. Please note that adding an icon or a description to the SDK_TASK line, the icon and description specified in the capability file will be overwritten. The external commands will be interpreted in the same order as they were on the extended menu. Capability files are read in creation order, i.e. the files that were created first will be read first. The commands from the capability files are assigned to TASK_SDKn menu items in the order in which they are found in the capability file. If e.g. you create two capability files in this order: a.cap and b.cap, then a.cap would be read first, en b.cap second. If a.cap has 3 commands and b.cap has 2 commands, then the commands from a.cap would be represented by tasks TASK_SDK1, TASK_SDK2 and TASK_SDK3. The tasks from b.cap would be represented by TASK_SDK4 and TASK_SDK5. After you have created the file and defined the menu, put it in the following directory from the root of the SD card:
The full path to this directory is /mnt/sdcard/SdkRegistry/ If the connection with the SD card is made through HyperTerminal, the following command should be given at the terminal to force the changed block to disk:
When the TomTom GO starts, the SdkRegistry directory will be searched for the file 'TomTom.mnu'. If available and correct, the customized menu will show instead of the default menu. 3.4. Summarize TomTom.mnu A customized menu is defined by:
where
where
3.5. Custom Preferences In your custom menu, you can also specify a set of preferences tailored to your needs. To do that, you have to do two things:
The parameters are the same as for the main block. The preferences block can have more than one page. You define navigation between pages in the similar fashion as for the main block: the last menuitem could be the next preferences page, the first preferences page or the first menu page. 3.6. Overview menu items For more information on TomTom GO menu items, please refer to the manual that is provided with the TomTom GO. Blocks There are three blocks that can currently be defined in a menu file:
BTM_options At block-level, the following items can be defined to be shown at the bottom of the screen. Each menu-page of that block will show the BTM_options defined for that block.
Menu Items The following menu items can be used in the customized menu file for the main menu and the preferences menu. Special Tasks
Navigation
Downloads
Manage Maps
Favourites
Preferences
POI
Traffic
Miscellanious tasks
Downloads
Help
Phone
Multimedia
The following menu items can be used in the customized menu file for the map cursor menu. Cursor menu
4. How to add a colour scheme The TomTom GO comes with several map colour schemes, which can be selected by selecting 'Change Map Colour' from the Preferences menu. It is now also possible to create your own map colour scheme and add it to the list of schemes. 4.1. Example colour scheme Copy the following code into a file called 'mycolours.clr' or use the corresponding file from the /TomTomGO-SDK/examples/additional_configuration/ folder.
Put the file ‘mycolours.clr’ in a directory called 'schemes' from the root of the SD card. First-time SDK users will probably have to create this directory. Please note that the full path to this directory is /mnt/sdcard/schemes/ . On the TomTom GO browse to Preferences => Change Map Colours. Tap on the arrows to cycle through the colour schemes. A plug-in scheme will be available and selecting it will show you the new scheme 'mycolours'. 4.2. Creating a colour scheme Choose the name of your colour scheme and create a file with that name and the extension CLR. The name will be displayed on the scheme selection page, so choose a sensible name. In the .CLR file define the colours of the different components of a map; what colour do you want a park to have, how do you want a motorway to look like, a city, etc. The colours are defined by their RGB values: the red, green, and blue intensity values that are used to define a colour. The comment behind each set of values, which is preceded by either '//' or ";", describe which component of the map that line defines. Please note that the colour-definition on a line in the colour file is always assigned to the same component; the colour for woodland is always the 5th colour defined in the file, a runway always the 13th, etc. So, commenting out some line at the beginning of the file, should give you some funny results, as each component gets the previous component's colour-definition. Refer to the comments of the example 'mycolours.clr' to see which component of a map each line represents. 4.3. Adding a colour scheme Put a valid CLR file in the following directory from the root of the SD card:
The full path to this directory is /mnt/sdcard/schemes/ When selecting a colour scheme from the Preferences Menu, a plug-in scheme will be available. Selecting it will show the newly created colour scheme 'mycolours'. 5. How to disable plug-and-play on the serial port The default plug-and-play program uses the serial port. This can cause problems for other applications that also need to use the serial port. To disable the plug-and-play program, place an empty file in the root of the sdcard or harddisk, called "TTPnPD". During startup, this file will be started in stead of the default plug-and-play program. Because an empty file is not a valid executable, execution will fail and no plug-and-play program will be running. |