diff options
| author | Pierre Ossman <ossman@cendio.se> | 2014-09-17 13:55:18 +0200 |
|---|---|---|
| committer | Pierre Ossman <ossman@cendio.se> | 2014-09-17 13:55:18 +0200 |
| commit | 093978008b655038fb677e244bf0fc6d21a3b39f (patch) | |
| tree | df059abca662973da99d2de3872e415c90e41d2f /doc/TODO | |
| parent | 2b3ea10c094f125aa26bc9b52ff8337d8af7a949 (diff) | |
| download | tigervnc-093978008b655038fb677e244bf0fc6d21a3b39f.tar.gz tigervnc-093978008b655038fb677e244bf0fc6d21a3b39f.zip | |
None of these files are relevant today
Diffstat (limited to 'doc/TODO')
| -rw-r--r-- | doc/TODO | 31 |
1 files changed, 0 insertions, 31 deletions
diff --git a/doc/TODO b/doc/TODO deleted file mode 100644 index 2069e694..00000000 --- a/doc/TODO +++ /dev/null @@ -1,31 +0,0 @@ - -* When running the UNIX vncviewer on a host with a different byte - order than the Xserver, the colors are incorrect. This happens when - using color depth 24 ("cutZeros"). Basically, the problem is that - the RGB24_TO_PIXEL32 macro is wrong; we need to swap endianess - in this situation. There seems to be something wrong with the local - cursor handling as well. - -* Change version strings. - -* Tight encoding support - -* Update vncviewer.man: many parameters are currently not documented. - -* When manually changing color level and running against an old server - (Xvnc from TightVNC 1.2.9, for example), the user should perhaps be - warned that vncviewer might crash. - -* Document the Tight protocol extensions in a text file. - -* All other features from the TightVNC 1.3 series: Filetransfer etc - -* Consider adding the toolbar from http://lars.werner.no/vnc/. - -* Implement support for rfbEncodingXCursor. When this is finished, it - should be safe to allow dynamic pixel format changes again, as long - as we only orders new pixel formats after recieving a framebuffer - update with real pixel data. - -* The vncviewer password dialog should probably display the server - name in the password dialog windows title. Wish from Gaetano Giunta. |