Virtual Keyboard changes in 3.1.1

That represents the facepanel layout of the new Apex consoles. I don't think this changes will be reverted.

Well actually, this is really confusing for non Apex users (which for now are most of us). It should be mirroring the lay-out of the console or programming wing that you are actually using. If you are using the software as off-line editor, you should be given the choice, maybe in the shell, maybe in the device settings.

It has always been the case that the keyboard represents the latest keyboard layout in the family. The previous keyboard represented the Gio/Ti/Ion Xe layout, so if you were working on Ion classic or Eos classic the same issue would apply. 

The core target/number sections remain unchanged between these layouts.

I agree that this could be confusing. I suggest submitting this as a feature request.

In my head, it would be best if it defaulted to the latest keyboard layout, but you could change this to older keyboard layouts in the user settings.

Or maybe event custom key layouts.

You took the words out of my fingertips. I understand mirroring the latest console but it seems to me that there are far fewer of those in the wild than all the most recent "legacy" line of EOS (as dsmurfin enumerated). It feels like there should be at least some delay of when the Virtual KB is changed and not necessarily at introduction. Alternatively an option to select (or default) based on console it is being run on or a Nomad option (like EOS vs Element). Another thought would be to have it as a Setup>Device>Displays option.

Feature request has been raised so please vote for it if you agree.

You took the words out of my fingertips. I understand mirroring the latest console but it seems to me that there are far fewer of those in the wild than all the most recent "legacy" line of EOS (as dsmurfin enumerated). It feels like there should be at least some delay of when the Virtual KB is changed and not necessarily at introduction. Alternatively an option to select (or default) based on console it is being run on or a Nomad option (like EOS vs Element). Another thought would be to have it as a Setup>Device>Displays option.

Feature request has been raised so please vote for it if you agree.

The bigger question is, why have the real buttons moved on the Apex consoles, since that certainly breaks some muscle memory...... ;-)

The vast majority of keys are in exactly the same place. The previous keypad layout is 8 years old. Times change, new functionality needs dedicated keys...