Closed GoogleCodeExporter closed 8 years ago
(Regarding Shortcut mappings config window, of course)
Original comment by zaha...@gmail.com
on 9 Mar 2013 at 2:49
Displaying nothing is confusing, since it would not be clear where to click to
set a shortcut. Whatever we put there must be wide enough to give the user the
idea that it is clickable.
Some options:
* <> what we have now
* '' empty string, probably too narrow
* None bit verbose
* Maybe we can use background color of the cell?
Any ideas?
Original comment by almar.klein@gmail.com
on 9 Mar 2013 at 11:10
As a gamer I've never found it problematic (in games' "control" configs) so
long as the assignment table is clearly visible.
Both <> and '' are non-standard. "None" might indeed be problematic if there's
a whole column of it. Shading is good, but you can't use it if the columns'
widths aren't set properly, otherwise there's a whole lot of gray.
1. The easy option is to use some obscure Unicode character like one of these:
○ ◌ ░
2. A better (and harder) option, and one that would support shading as well, is
to redesign the window: At the moment it's a wide tabbed table, and the lack of
a border between keys and values makes it confusing. Having a table that looks
"sunk" in comparison to the rest of the window (or otherwise making the cells
distinct from the "structure" - the tabs and the keys), and only as wide as
needed, would make identifying the cells as clickable easy.
A couple of links to elucidate (different tables, same idea):
http://docs.oracle.com/cd/E19365-01/819-6127/images/BPE_Configuration_display6.g
if
http://www.ivyteam.ch/downloads/XIVY/4.3.0/doc/guides/designerGuide_html/images/
ConfigurationManagement/configuration_editor_smart_table.png
PS - it would be useful to have an instruction like "Click the... to assign a
key"" (or something like that) under the tabs.
Original comment by zaha...@gmail.com
on 10 Mar 2013 at 1:46
yeah, having a visible border would probably do the trick. A small instruction
would make it even clearer.
Original comment by almar.klein@gmail.com
on 11 Mar 2013 at 9:28
As part of migrating our code repositories from Googlecode
to Bitbucket, all IEP issues are now tracked at
https://bitbucket.org/iep-project/iep/issues
To view this issue, use this link (with X replaced by the issue number):
https://bitbucket.org/iep-project/iep/issue/X
Issues on Bitbucket can be created by anyone. Commenting on issues requires
login via Bitbucket, Google, Twitter or Github.
Original comment by almar.klein@gmail.com
on 11 Jun 2013 at 2:40
Original issue reported on code.google.com by
zaha...@gmail.com
on 9 Mar 2013 at 2:48