Onscreen keyboard

**gti** · 12-07-2004, 03:53 AM

ive tried all the above and still no luck.

Trev

**Ninja Monkey** · 12-07-2004, 01:59 PM

Originally Posted by gti

ive tried all the above and still no luck.

Trev

You seem to be having a different problem, the keyboard is actually clickable for you (seeing as the home button works) but it's not sending the keys to the dialog...

I'm guessing my code to find the dialogs handle is either failing or mistaking it for some other application you have running...can you try exiting out of absolutely everything you can (including hidden processes in task manager) and trying again?

Worth a shot

**gti** · 12-08-2004, 04:20 AM

Ninja Monkey,

Ill give that a go in a bit, im at uni at the mo. Ill shut down all background stuff and let you know how it goes.

Trev

**gti** · 12-09-2004, 05:55 AM

Ninja Monkey the problem is solved. Im running sygate firewall on both internet pc's, and for some reason its screwing with the osk. So i turned this off for a sec and all is solved. Clearly i will have no need for a firewall on my car pc

Regards

Trev

**bjorker** · 12-09-2004, 11:37 AM

Yeah, I can confirm this.
I was having the same problems with the onscreen keyboard, but after disabling sygate firewall it works like a charm.

**Ninja Monkey** · 12-09-2004, 01:59 PM

Excellent! Glad you got it sorted (and it doesn't mean any extra coding for me!)

**Wax Man** · 12-10-2004, 03:55 PM

My osk works if I launch destinator from the button in frodoplayer, but not from the desktop shortcut.

bye bye desktop shortcut!

thanks for all the hard work

**hemandk** · 12-10-2004, 05:44 PM

Well it seems that mine did not work either, just made a sound when i tried to press the buttons. Turned off the Win Xp SP2 firewall and it worked like a charme...

Damn i hate SP2

**gti** · 12-10-2004, 05:56 PM

so even xp fw can screw things up... hmmm wonder why a firewall causes this. You got any ideas Ninja Monkey??

Trev

**Ninja Monkey** · 12-10-2004, 06:28 PM

Under 1.1.2 the frontend talks to the D3 client through a TCP/IP connection, so I can see why a firewall might block it...

however, the last few betas are complete single applications and don't use anything like that at all! Why a firewall would block API calls is beyond me