Skip to content

Commit

Permalink
*** empty log message ***
Browse files Browse the repository at this point in the history
git-svn-id: svn+ssh://svn.code.sf.net/p/turbovnc/code/trunk@823 799e4f7b-5fd2-41f6-823c-2ecc41bc7f0b
  • Loading branch information
dcommander committed Nov 24, 2008
1 parent 1d23ed3 commit cc27982
Show file tree
Hide file tree
Showing 2 changed files with 18 additions and 0 deletions.
9 changes: 9 additions & 0 deletions vnc_unixsrc/TurboVNC-ChangeLog.txt
Original file line number Diff line number Diff line change
Expand Up @@ -90,6 +90,15 @@ Fixed a bug in the color conversion routines of TurboJPEG/mediaLib which
caused the Solaris TurboVNC Viewer to display spurious multi-colored vertical
lines when 2X or 4X subsampling was used.
-------------------------------------------------------------------------------
[17]
When requesting a Lossless Refresh using the TurboVNC viewer on a Linux or
Solaris/x86 client, the pixels obscured by the F8 dialog will be regenerated
using lossy compression after the lossless refresh has occurred. This makes
the lossless refresh somewhat ineffective. We were not able to find a fix
for this in 0.5, but as a workaround, you can now use the hotkey sequence
CTRL-ALT-SHIFT-L to request a Lossless Refresh without popping up the F8
dialog.
-------------------------------------------------------------------------------


===============================================================================
Expand Down
9 changes: 9 additions & 0 deletions vnc_winsrc/TurboVNC-ChangeLog.txt
Original file line number Diff line number Diff line change
Expand Up @@ -90,6 +90,15 @@ Fixed a bug in the color conversion routines of TurboJPEG/mediaLib which
caused the Solaris TurboVNC Viewer to display spurious multi-colored vertical
lines when 2X or 4X subsampling was used.
-------------------------------------------------------------------------------
[17]
When requesting a Lossless Refresh using the TurboVNC viewer on a Linux or
Solaris/x86 client, the pixels obscured by the F8 dialog will be regenerated
using lossy compression after the lossless refresh has occurred. This makes
the lossless refresh somewhat ineffective. We were not able to find a fix
for this in 0.5, but as a workaround, you can now use the hotkey sequence
CTRL-ALT-SHIFT-L to request a Lossless Refresh without popping up the F8
dialog.
-------------------------------------------------------------------------------


===============================================================================
Expand Down

0 comments on commit cc27982

Please sign in to comment.