Currently the Dpad on the n810 acts like a tab. Pushing up or down jumps from field to field. I would like to remap the up down to the cooresponding arrow keys on a keyboad or at the very least pgup/pgdn but I really don't know how to write that in Xmodmap. I'd like R_shfit + dpad to act like it does now.

Help?

It kinda surprises me that there is no scroll wheel or simple scrolling mechanism on a device designed around the web. Oh well, still loving it.

Anyone have any answers?? even the keycode?

It acts exactly like (and is mapped to) the arrow keys. If you use a bluetooth keyboard, it will do the same; also, that behavior is largely constrained to the web browser; in other places, they behave more normal.

There's at least 3 options.

First, you can leave the config alone, and scroll by holding the d-pad down in whichever direction. (Perhaps you didn't know about that?)

Second, you can make some config changes so that arrow keys are not used for navigating; I don't know of a way to make shift+arrows still do s-nav, though, so you lose that ability entirely.* There's also stuff in that thread for making them page down, not scroll down, if you like that.

Third, you can use a greasemonkey script to put page-down buttons over top of everything; preserving snav.


*While looking for those links, I got curious and looked over here; looks like instead of disabling snav, you can set snav.keyCode.modifier = SHIFT... I have an N800, so without a shift key, I can't really try it, but you might give it a shot. Some reports indicated that some settings didn't stick, i.e. microb resets them on startup; but that was an old version, and it may be better now.

I was never able to get snav to work on shift, unfortunately.

I ended up doing the config change method, but you should also be able to remap up and down to pageup and pagedown and shift to up and down, but it would change how that acts in all applications. Just remember for the Xmodmap file that X things pageup is called Prior and pagedown is Next, and shift is the second listed function for a key.

Wouldn't it be better to map up and down as Up and Down, and shift+up and shift+down as something else, say F23 and F24; then use snav.keyCode.up = DOM_VK_F23, and such?

Or does that not stick, either?