With Player Next Gen, the Intuiface keyboard by default is OFF. Therefore you need to open the player settings at the player PC itself, and select “Use Intuiface Keyboard”, (at least for windows PC’s). Its not critical, but easy to forget, and it’s just not convenient.
In Admin console, when you select a player, you can choose player preferences such as ‘show the experiences panel’ or ‘launch last xp’. Why can’t we put ‘use intuiface keyboard’ in this player preferences panel? This seems to make a lot more sense, rather than needing to do this at the player pc itself…
Player 8 on Android and iPad has the virtual keyboard disabled, since the OS offers its own keyboard.
Player 8 on BrightSign has the virtual keyboard enabled and on by default, since BrightSign doesn’t offer any alternative.
Player 8 on Windows used to have it disabled (as in, not available), because most the Player 8 use cases we saw “at the beginning of Player 8” were used on desktops / laptops for project reviews, or in a Web Browser, thus on devices with a physical keyboard. It was more annoying then to disable it than to enable it. This most likely changed over the last few months.
Also, Player Settings on the Player itself are available to anyone. Player settings in the Share & Deploy Console are only available to Enterprise users. Being able to enable / disable that virtual keyboard was deemed a feature that had to be available to anyone.
The idea you have is already in our product team’s roadmap, although not at the top of the list of priorities at the moment. This post will definitely put a +1 on that request.
My take is there are actually 2 “demands” here
On Player 8 for Windows, make the Virtual Keyboard enabled by default
For all the Player 8 platforms where the Virtual Keyboard can be enabled or disabled, move that setting from the local Player settings (again, available to all Intuiface users) to the Share & Deploy Player preferences (only available to Enterprise users)
and figure out where to leave the setting for non-Enterprise users
The first one is easy to implement, if we get enough requests / votes.
The second one isn’t that easy, as it’s not just a “dev resource” question.
The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.
