Search results

I can get loxodo.py to run if I first run wxpython, then from within wxpython navigate to where loxodo.py is and execute it by the command line. Is there a way to encapsulate all of this so I can run it from an icon?

I havn't noticed any difference. Of the issues I've run into, my proiritys are: 1) get the Pandora to reconnect after it has been asleep so I don't have to turn off bluetooth and turn it back on again. 2) get a decent default gui for the pandora 3) get search by street number working 4) If...

Damn! I read that as Lego LED. This lead me to think I could snap on my own iluminated logo :) I believe the lego patents have expired, so you could build a lego compatible LED, you just could not have the lego logo on it.

Look at Navit. This is currently running on the Pandora. It is OK, but it still needs work. It currently won't navagate to a street address, only a street, which can be problematic on very long streets. It plays stupid computer tricks like saying "take ramp right" instead of "take ramp right...

WIFI only as long as I can still get GPS, and the keyboard does not have a double wide space key.

One might be able to print an adiquate case top, but keymat? Not currently possible.

This is good to hear, but can we also get an alternate case and keymat that have the space key split in two?

I used to like Ubuntu back when it used Gnome 2.0. Then for some inexplicable reason both Ubuntu and Gnome decided that they needed to convert their user interface to be tablet interfaces instead of the desktop interfaces they used to be. For a while I used the Gnome Classic interface, but...

(sorry, taking this quote out of context and making it look like you were arguing for the other side...) We can easily make it visually distinguishable by making it a different color, (how about day glow yellow?) we don't need to make it double wide for that. If we need to be able to feel the...

On the Pandora/pyra, you hid ALL the keys with your thumbs. There is no need for the space key to be bigger.

In order to get the correct relative positions of the keys in a Dvorak keymap on Pyra, the keys must go where shown in the attached image. Well, Damn! I'm not allowed to add attachements. I guess I'll just have to draw it. --------------------------------------------- | 1 | 2 | 3 | 4 | 5...

Because on the Dvorak keymap the keys to the right of the location of the 'M' key (same location on Dvoark & QWERTY) are: 'w', 'v', and 'z', so 'w' and 'v' need to go in the space taken by the space bar.

Can you please not make the space key two keys wide? That makes a dvorak keymap impossible.

Normal USB 2.0 operation is to attempt to talk to a newly plugged in device in High Speed mode, and when that fails try again in low/full speed mode.

Thank you. I have been waiting a long time for this. Downloading now.

As long as any key can be remapped to any other key, and there are no double wide keys, two shift keys are not a problem.

I think I have made it VERY clear I have an issue with a double wide space key in that location. I guess I just don't count.

as long as the "sticky altGR" key is re-mappable, that is just enough to make Dvorak possible. A few punctuation keys would have to move, but I can live with that.

If you must have a double wide space key, put it to the left of the 'z' key, and put ',' and '.' back where they belong.

Cut the space bar in half, or put it to the left of the 'Z' key. A double wide key where it is now precludes the Dvorak keymap.