View Single Post
Old 09-22-2008, 04:30 PM   #5
-Thomas-
Addict
-Thomas- once ate a cherry pie in a record 7 seconds.-Thomas- once ate a cherry pie in a record 7 seconds.-Thomas- once ate a cherry pie in a record 7 seconds.-Thomas- once ate a cherry pie in a record 7 seconds.-Thomas- once ate a cherry pie in a record 7 seconds.-Thomas- once ate a cherry pie in a record 7 seconds.-Thomas- once ate a cherry pie in a record 7 seconds.-Thomas- once ate a cherry pie in a record 7 seconds.-Thomas- once ate a cherry pie in a record 7 seconds.-Thomas- once ate a cherry pie in a record 7 seconds.-Thomas- once ate a cherry pie in a record 7 seconds.
 
-Thomas-'s Avatar
 
Posts: 325
Karma: 1725
Join Date: Dec 2007
Location: Münster, Germany
Device: iRex iLiad v2
Quote:
Originally Posted by genome2k View Post
2. Inside of emelFM2 I found when sometimes I occassionally touched keys of iLiad, for example, the page back/forward key, it will deliver some commands to iliad. And iLiad could be for a long time showing a busy status with flash red LED on the top. Is there any instruction regarding the functions of these keys on iLiad.
This isn't a big issue, it's because of the hardware and software design. To sum it up: Hardware buttons are controlled by the content lister and (some) key strokes are "redirected" to the currently running application. The application (in your case emelFM2) has to handle these key strokes correctly, i.e. to move to the next page if the page bar has been moved.

The content lister activates the busy led as soon as you press a button and waits until the running application "answers" with some action. As emelFM2 doesn't handle key presses at all, the led continues to show a busy status while your device should still be controlable as usual.
-Thomas- is offline   Reply With Quote