iGuidance v.3 - teaser picture(s)

**Marvin Hlavac** · 06-11-2006, 10:27 AM

Good feedback on the OSK. I tend to agree QWERTY is easier for all of us and there still is some unused space on the screen because OSK could (should?) cover the whole screen (no reason to see some of the map around it).

Btw, let's keep in mind this is just a Beta version we are looking at. It's very close to the final version, but still a Beta.

**nameeri** · 06-11-2006, 01:31 PM

give em feedback for us Marvin!

**Marvin Hlavac** · 06-11-2006, 01:34 PM

Done ;-)

**PURDooM** · 06-11-2006, 02:36 PM

Originally Posted by b8bboi

Marvin, thanks for the OSK screenshot.

Frankly, it disappoints me a little. First, as replicant said, why not QWERTY? Second, why couldn't they squeeze the numeric keys in? Third, why couldn't they squeeze in more than 1 line for the street prediction window? Why not use a little more screen estate? I was able to do all that in iGMon and my buttons are still plenty big.

http://i33.photobucket.com/albums/d86/b8bboi/iGosk.jpg

Hopefully, it's skinnable or at least configurable.

B8bboi: If the majority of the OSK code is the same, you can make that suggest window taller or shorter at runtime (with your program) and it will have more entries on it. I think the command to do that is setwindowpos (onto the hwnd of the suggest box) or something along those lines. When v3 is out and you start making iGmon ill get you the correct api call for that

**PURDooM** · 06-11-2006, 02:38 PM

The A-Z format that they are using is what has been used on the iGuidance Pocket PC version in the past. I think they are just standardizing all the versions.

**Marvin Hlavac** · 06-11-2006, 02:56 PM

I just installed iGuidance 3 on a PDA and I see why QWERTY could be a problem there. On a PDA even in the landscape mode you could have difficulty fitting 10 keys across the screen from left to right. That's what QWERTY has in the top letter row :-(

I guess it comes down to what is more important: the convenience of the familiar QWERTY keyboard or the size of keys. Most users would likely soon complain about too small keys than about the non-QWERTY OSK.

**DK888** · 06-12-2006, 10:05 AM

This is GREAT, can't wait to get my hands on it!

**spyhunter** · 06-12-2006, 11:47 AM

looks great, looking forward to it

**b8bboi** · 06-12-2006, 11:55 AM

Originally Posted by PURDooM

B8bboi: If the majority of the OSK code is the same, you can make that suggest window taller or shorter at runtime (with your program) and it will have more entries on it. I think the command to do that is setwindowpos (onto the hwnd of the suggest box) or something along those lines. When v3 is out and you start making iGmon ill get you the correct api call for that

Purdoom, I'm not sure that window is gonna be a separate child window that we can grab the handle and change the size from outside.

I guess it comes down to what is more important: the convenience of the familiar QWERTY keyboard or the size of keys. Most users would likely soon complain about too small keys than about the non-QWERTY OSK.

I agree with you. The size of the buttons is still more important. Small keys make it almost unusable. Non-QWERTY keys (and no numeric keys) only make it annoying. Then again, I thought the checkbox for UMPC or AutoPC was supposed to take care of these differences?

**Marvin Hlavac** · 06-12-2006, 12:13 PM

Originally Posted by b8bboi

...and no numeric keys...

Both letters and numbers are likely not needed most of the time, since we first enter street name on one screen and in another step we enter street number in a different screen.

Originally Posted by b8bboi

...I thought the checkbox for UMPC or AutoPC was supposed to take care of these differences?

That is true.