1) The GUI offers the option to be able to redefine keys. As long as the option is there, it's a bug for it to not work.
2) Redefining keys is a standard part of GTK (or Gnome--I'm not sure which). It's a handy feature that works everywhere else I've tried it. I know that Gnome delights in removing useful features in the name of simplification, but doing so is a Bad Thing.
3) I don't see how it's possible to design a full-featured VNC client without at least one keyboard shortcut. Once you switch to fullscreen, you have to have some way to get back out. Adding a button to switch back to normal mode would either potentially get in the way or require a VNC toolbar or something, which would break the fullscreen. Vncviewer handled this situation well. If you hit F8, it would pop up a menu. One of the items on that menu was one to send F8 to the remote machine. (There are many thing that vncviewer does wrong, but this isn't one of them.)
I disagree for three reasons:
1) The GUI offers the option to be able to redefine keys. As long as the option is there, it's a bug for it to not work.
2) Redefining keys is a standard part of GTK (or Gnome--I'm not sure which). It's a handy feature that works everywhere else I've tried it. I know that Gnome delights in removing useful features in the name of simplification, but doing so is a Bad Thing.
3) I don't see how it's possible to design a full-featured VNC client without at least one keyboard shortcut. Once you switch to fullscreen, you have to have some way to get back out. Adding a button to switch back to normal mode would either potentially get in the way or require a VNC toolbar or something, which would break the fullscreen. Vncviewer handled this situation well. If you hit F8, it would pop up a menu. One of the items on that menu was one to send F8 to the remote machine. (There are many thing that vncviewer does wrong, but this isn't one of them.)