Update TODO listi and README

1 files changed, 39 insertions, 64 deletions

diff --git a/NxWidgets/TODO.txt b/NxWidgets/TODO.txt
index 1c4632d27..105be3737 100644
--- a/NxWidgets/TODO.txt
+++ b/NxWidgets/TODO.txt
@@ -1,12 +1,26 @@
 NxWidgets
 ---------
 
+  Title:        LARGE BITMAP SUPPORT
+  Description:  In CImage, m_origin.x and .y need to be allowed to go
+                negative so that you can pan through a large image.
+  Status:       Open
+  Priority:     Low
+
+  Title:        GLYPH BACKGROUNDS
+  Description:  For most glyphs, background could is set to the currently
+                selected background color.  An option should be to set the
+                background of glyphs (only) to transparent.
+  Status:       Open
+  Priority:     Low for now
+
 NxWM
 ----
 
  (4) General Issues
- (3) NxConsole Issues
- (1) CHexCalculator Issues
+ (0) NxConsole Issues
+ (0) CHexCalculator Issues
+ (3) CMediaPlayer Issues
  (1) Platform specific Issues
 
 See also the NuttX TODO list graphics/ section for related issues.
@@ -16,7 +30,7 @@ o General NxWM Issues
 
   Title:       DISPLAY INTIALIZATION
   Description: During the initialization of the display, the basic frame of the
-               start window is draw momentarily.  The is just the empty window
+               start window is drawn momentarily.  The is just the empty window
                frame.  This is a consequence of how NX creates windows:  The
                are enabled all of the time so the windows are visible when they
                are being created. The solution would be to add some disable
@@ -49,7 +63,7 @@ o General NxWM Issues
 
   Title:       THREAD SAFETY
   Description: I am not sure how thread-safe the NxWidgets are.  There is
-               is very little mutli-thread in the widgets now.  The "NX listener"
+               is very little multi-thread in the widgets now.  The "NX listener"
                thread interacts to update mouse (and keyboard) data but all
                of the heavy work is done on the "start window" thread.  I think
                everything is okay now, but it may be necessary in the future
@@ -74,74 +88,34 @@ o General NxWM Issues
 o NxConsole Issues
   ----------------
 
-  Title:       MULTIPLE COPIES OF AN NxCONSOLE
-  Description: From the start window, you an create multiple copies of the
-               NxConsole.  However, there is a problem in the current
-               implementation:  Each NxConsole receives its input from the
-               serial console so, for example, it you enter text one character
-               will go to one NxConsole instance and the next character goes
-               to a different instance.  That is correct behavior within the
-               current design, but not very usable.  We need a mechanism to
-               assure that the top window is the one that receives all
-               eyboard input.  NX already provides this capability with its
-               nx_kbdin interface(), but that is not currently used.  At present,
-               NxConsoles get their input from /dev/console which is the serial
-               port.  The necessary change is to create an NX input device for
-               /dev/console that will get its input from NX.
-  Status:      Closed with was fixed with the check-in of 5/20/2012 (about
-               SVN version 4755).  The fixed version is available in SVN but
-               won't be in a released version until NxWidgets-1.2 is released.
-  Priority:    Medium high, basically prohibits the use of multiple NSH windows.
-
-  Title:       CLOSING AN NxCONSOLE
-  Description: If you open multiple NxConsole applications, they all receive
-               serial input (as noted in the previous bug).  However, if
-               you close one of the NxConsoles, then the others no longer
-               received input (or no long generate output -- that cannot be
-               distinguished).
-  Status:      Closed with was fixed with the check-in of 5/20/2012 (about
-               SVN version 4755).  The fixed version is available in SVN but
-               won't be in a released version until NxWidgets-1.2 is released.
-  Priority:    Medium high, basically prohibits the use of multiple NSH windows.
-
-  Title:       DOUBLE DISPLAY UPDATES
-  Description: When the NxConsole window is first opened, there are usually
-               double updates, i.e., the display forms twice.
-  Status:      Open
-  Priorioty:   Low, this would be necessary to fix to productize the windows.
-
 o CHexCalculator Issues
   ---------------------
 
-  Title:       NEW DATA ENTRY IS APPENDED TO PREVIOUS RESULT
-  Description: For example 1+2= and 3 is shown.  But if you enter 4, then
-               34 is shown.  You have to manually clear the calculator ("C")
-               before entering the next number.
+o CMediaPlayer Issues
+  -------------------
+
+  Title:       SCROLLING FILE LIST
+  Description: Current implementation uses a CListBox which can only show a
+               fixed number of files.  Perhaps CMediaPlayer should use
+               something like CScrollingTextBox.
   Status:      Open
-  Priority:    Low, this is only a demo.  This would, of course, have to be
-               fixed if you wanted a production quality calculator (but then
-               you would probably also want to add quite a few more features
-               as well).
+  Priority:    Low for now
+
+  Title:       PLAY PROGRESS FEEDBACK
+  Decription:  Need a way to know the position in the file, how long the
+               file is (in minutes), and an indication when playing
+               complete.
+  Status:      Open
+  Priorit:     Medium.  Certain affect usability.
+
+  Title:       NO BALANCE/TONE/EQUALIZER CONTORLS
+  Description: The title says it all
+  Status:      Open
+  Priority:    Medium.  That is big functional limitation.
 
 o Platform specific Issues
   ------------------------
 
-  Title:       MISSING TOUCH RELEASE
-  Description: Using the STM3240G-EVAL board with the STMPE11 touchscreen, you
-               will find that there are occasional missing indications of when
-               you release a icon.  This is believed to be a data overrun in the
-               STPMPE11 data path.  The STMPE11 generates data a very high
-               rate and it is believe that it sometimes misses the interrupt
-               that indicates that the touch is released.  The symptom in NxWM
-               is that you touch an icon, it is highlighted but when you release
-               the touch nothing happens.  The icon stays highlighted.  Touching
-               the icon again usually works around this problem.
-  Status:      Closed with was fixed with the check-in of 5/21/2012 (about
-               SVN version 4758).  The was change made to NuttX, not NxWidgets.
-               The fixed version is available in SVN but won't be in a released
-               version until NuttX-6.198 is released.
-  Priorioty:   Low, but really annoying.
-
   Title:       BUGS WHEN CANNOT READ FROM LCD
   Description: There is a kludge in there to handle the case where we cannot
                read the background data because the LCD does not support read
@@ -156,3 +130,4 @@ o Platform specific Issues
                places as well and begs for a better solution.
   Status:      Open
   Priority:    Medium-Low
+