I found the problem, and it was basically the same as for cjpeg. The empty_output_buffer() callback is part of the API, and when you forced it to check free_in_buffer, you were no longer backwards compatible and the tight encoder of course broke down. I don't understand how this bug wasn't present when Adam tested.
Anyway, I think that we should retain libjpeg compatibility. As your new huffman encoder outputs several bytes at once, that might mean a performance hit though. Could you see how much damage it does to replace all *buffer++ = with something like the previous emit_byte()? Rgds -- Pierre Ossman OpenSource-based Thin Client Technology System Developer Telephone: +46-13-21 46 00 Cendio AB Web: http://www.cendio.com
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
