| Subject: Another Conflict? |
Author:
Sophie
|
[
Next Thread |
Previous Thread |
Next Message |
Previous Message
]
Date Posted: 16:03:55 01/07/03 Tue
It's me again. I may have stumbled across another conflict. This one with DateBk5.
I had the datebook hard button mapped (by QLaunch) to menu, keyboard and brightness - all important if you don't want to open your Tungsten. If I have DateBk5 open, and I press and hold the datebook button, it begins scrolling through its various views. So if I am in day view in DateBk5, a "short" hold, which should bring up the menus, first takes me to week view and then brings up the menus, but they are the menus (in fact one only)appropriate to week view, not the full array I want.
If I use the address, todo or notepad keys for menu, keyboard and brightness, I run into the split screens that DateBk5 normally produces. In othet words, it seems the QLaunch mapping does not override, or completely override, what DateBk5 wants to do with press and hold.
This behaviour does not occur when the built-in Datebook is open. And it seems it only occurs if the QLaunch mapping is to a "special". It is all right if the mapping is to an application.
I haven't explored this fully - there might even be some DateBk5 preferences that can overcome it, but I thought I should report as soon as I found the behaviour. Or I'm doing something wrong, or you already know about it and there's a workaround.
So for the time being at any rate, I'm going to keep menu, keyboard and brightness away from those four major hard buttons. That means taking them to our friend the five-way navigator - dare I say it, another reason for making the up and down available????? (For me, using the voice recorder button is not an option - I want press and hold there to retain its intended function.)
- Sophie
[
Next Thread |
Previous Thread |
Next Message |
Previous Message
]
| |
