Your message dated Sat, 24 Oct 2009 15:43:45 +0100
with message-id <[email protected]>
and subject line Re: ltris: resistance to control configuration
has caused the Debian Bug report #186693,
regarding ltris: resistance to control configuration
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
186693: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=186693
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ltris
Version: 1.0.3-2
Severity: normal

When I go to configure the controls player one, and have selected an item, and
am being asked to provide a keystroke to configure the item, Ltris blatantly
refuses to recognise that I have hit certain keys, in fact, most of the keys on
the keyboard.  These keys have at least differed partially on executions.  I
can't figure out any pattern.

-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux nova 2.4.20 #4 Thu Mar 27 01:30:49 UTC 2003 i586
Locale: LANG=en_GB, LC_CTYPE=en_GB

Versions of packages ltris depends on:
ii  libc6                         2.3.1-14   GNU C Library: Shared libraries an
ii  libsdl-mixer1.2               1.2.4-1.1  mixer library for Simple DirectMed
ii  libsdl1.2debian               1.2.4-1    Simple DirectMedia Layer



--- End Message ---
--- Begin Message ---
I've experimented with this a bit and have discovered that it's not really a
bug so much as a lack of documentation.

The program prevents the user from selecting a key that is already in use
for another function.

Unfortunately the program doesn't list which keys are used anywhere. There
are several short-cut keys for various functions that can only be discovered
by examining the code.

If upstream was active I'd suggest asking them to document the key mappings
and maybe also to make the program beep if an in use key was selected by the
user for a function.

-- 
Colin Tuckley      |  +44(0)1223 293413  |  PGP/GnuPG Key Id
Debian Developer   |  +44(0)7799 143369  |     0x1B3045CE

Good advice is something a man gives when he is too old to set a bad
example. - La Rochefoucaud


--- End Message ---

Reply via email to