Closed GoogleCodeExporter closed 8 years ago
Original comment by scottaki...@gmail.com
on 7 Oct 2010 at 11:23
Hi! For me that wouldn't be good, as I'm mainly using it for Blender tutorials,
and there Shift+4 or Ctrl+4 or Shift+Ctrl+4 mean exactly that! (all related to
selecting the layer 4). So a "$" symbol might be confusing for people following
the tutorial.
Original comment by simonett...@gmail.com
on 20 Oct 2010 at 3:46
What I really think is that it should have an option to enable and disable this
option.
Original comment by fernando...@gmail.com
on 20 Oct 2010 at 2:52
OK, that would work for me, but I don't get why would showing the result would
be useful. I think that what you want to show are the keys you are pressing
during some process other than write (where you can see the outcome on screen).
In what scenario are you needing that functionality? (I'm just curious!!! not
trying to be annoying, sorry if I was). I know this is not a blog, so if my
comment is out of place, please delete/ignore.
Original comment by simonett...@gmail.com
on 21 Oct 2010 at 12:44
I think it would be nice because different keyboard layouts do not
have all the keys we get when combined with SHIFT in the same place.
For example, in br_abnt2 The " (double quote) is together with the
' (single quote) key.
To illustrate, in Vim, typing 0 does something different than typing ) (which
we get holding Shift while hitting 0), or " and ' also do very different
things. Notice that 0 and ) are in the same key and so do " and ' for example.
Here we have some examples (screenshots) of in how different positions
"shift-keys" are placed.
http://en.wikipedia.org/wiki/Keyboard_layout
Original comment by fernando...@gmail.com
on 21 Oct 2010 at 11:51
showing the key label might be useful with --old-keys:
then you can better see what you've typed.
Original comment by susefroh
on 11 Nov 2010 at 11:54
I am thinking this should be merged into Issue 46.
Original comment by livibet...@gmail.com
on 15 Aug 2011 at 2:53
merge reason will be stated in Issue 72.
Original comment by livibet...@gmail.com
on 18 Aug 2011 at 4:08
Original issue reported on code.google.com by
scottaki...@gmail.com
on 7 Oct 2010 at 11:22