Hi!
I´ve installed a Windows7 VM in english, Keyboard was German (Germany).
Also was the Keyboard on my iPad a QWERTZ (German) Keyboard.
If I type via my iPad, the VM register an english keyboard (german mapping on iPad, but the VM means he has an english one).
I´ve also tried to setup an english keyboard on the iPad, but the same issue...
Any ideas, how I get running an german keyboard mapping between the iPad App and my W7 VM???
Thanks a lot, Hannes!
Are you on View 4.6? There was some compability issues with View 4.5 and the iPad client.
// Linjo
Yes, I´m on 4.6 with all components...
cu Hannes!
Hi!
I can confirm, that the issue occurs only on Windows 7 VMs!!
We have tested OS language "english" and "german", with the keyboards "English (US)" and "German (Germany)"...
We got many support requests from our users...
Thanks, Hannes!
Hello!
We have the same issue here. All components are View 4.6. Virtual Desktop is Windows 7 X64. The Keyboard layout should be german but is english.
Is there any solution for this?
Thanks,
Andi
Hi!
Sorry, I doesn´t get any feedback about this...
Any ideas, Community?
cu Jo
In future releases, we are adding in international keyboard support for the major languages we usually support.
More on this later...
Tedd
perfect.
please bring this feature asap, many customers in EMEA are using the Client and got problems with their keyboards.
thanks Hannes
upcoming release of View Client for iPad will solve this issue.
Anyone got any news on this? I'd characterize this as a fairly significant shortcoming in the client, and it's a major showstopper for our customers (in Norway).
Hi stkristobal,
No, at this moment I haven´t news about the keyboard issue.
I think, there will be a upcoming update with View 5.
I´ll keep you updated!
cu Jo!
We are working hard to get this into the next (post 5.0) release of View. A workaround is to set the VDI to Engliish input and the iPad to the european input. It seems to work well in most use cases.
Hi!
Today i installed the latest update of te View Client for iPad (Version 1.2) but the issue remains. This is bad because it is a "showstopper" for using iPads with View (and Androids) with View Desktops. Because we want to use the same virtual Desktop on the iPad and on Workstations switching the default text input language of ethe VDesktop to english doesn´t work for us.
Is there a solution in the pipe?
Thank you
Andi
I second that. This is shocking prioritizing by Vmware. This has been reported for 6 months and honestly can't be that hard to fix. It's keyboard-mapping, it's not like everything has to be built from ground up (or atleast I hope not).
Most people in the world DON'T use US keyboards.
Sure, I confirm that.
In the actual situation, View Client for iPad was not usable for us and many customers around the world with this really big bug!
Very interesting is, that the localization support was build in with version 1.2, BUT NOT THE KEYBOARDS!
THis is a change that is needed in the Broker for View. The fix is slated for the next release of View in 2012. We apologize for the issues.
It is not a simple fix at all because of Virtual keyboard layout sync is needed. It is just not client changes.
Well 2012 is a bit vague; are we talking Q1 or Q4 here?
If it's a year away I'm certainly selling XenDesktop for our next project. Taking a year (this was reported in May) to fix such a blatantly obvious issue is simply not taking your customers seriously.
We are looking at earlier that "one year away" . We are working quickly to get this into the next rev. It is "new" issue because View and virtual keynoard layout sync is a new problem.
How is it a 'new' problem? This thread was started in April.
Without going into detail :
It is a 2 stage fix on a VERY large piece of software. One for the client (this is the first version with international keyboard input). then the Server piece to allow the layout sync. In the docs, there is a work around for this until the server piece is fixed.
Make the keyboard layout on the VDI English and the iPad layout to your preferred language. this will work fine. Yes it is not what we all want for now, but it works. Like I said, this is not an easy fix to implement, so a little patience is asked.