WRT keypad navigation?

[InYourDreamz]

Hi guys,

How do you do keypad navigation for 3rd ed? By default i see the mouse pointer on my widget ... and that's ugly.

[InYourDreamz]

ok, I found the answer

widget.setNavigationEnabled(false);


but there's more problems ... how do you handle the navigational sequences? How do I allow DIV navigation instead of the link anchor tag? At the moment, it will only navigate when it's a link but when I have a list that are all in DIV blocks, it doesn't scroll because it's not selected. Coding for touch screen was a lot easier ... omg.

And how do I scroll inside a DIV??

[jappit]

Hi InYourDreamz,

as from my experience, key-based navigation only allow to move focus through A elements. So, the solution would be to convert your DIVs into A elements.

As a tip: when converting a DIV into an A element, specify the 'display: block' CSS rule for it, since A elements display inline by default.

Pit

[InYourDreamz]

Got it Jappit! What about the sequence of navigation? Sometimes it jumps around. For example ...

Imagine 2 rows of links, the top one has 2 blocks left and right while the bottom has 4.

_______________ _______________
| | |
| Link 1 | Link 2 |
|_______________|_______________|
| Link3 | Link4 | Link5 | Link6 |
|_______|_______|_______|_______|

Hope the cool ASCII diagram shows up correctly.

It could navigate to Link1, Link2, Link3, Link6, but never Link4 and Link5. I've thought of using tabindex, but that doesn't make sense since keypress isn't tab

[allanbezerra]

Hi all,

Take a look on GuaranaUI Library.

Guarana components has keypad navigation support by default.

http://wiki.forum.nokia.com/index.ph..._for_Nokia_WRT

-- Allan Bezerra

[allanbezerra]

Hi,

put it in your code:

if (window.widget) {
widget.setNavigationEnabled(false);
}

-- Allan Bezerra