From: Loris B. <lb...@lo...> - 2008-08-06 10:44:58
|
On Wednesday 06 August 2008 09:52, Constantin Kaplinsky wrote: > Hello Loris, > > >>>>> Loris Boillet wrote: > > > > With the RFB protocol, if depth is set to 24, then the actual nb of bits > > per pixels sent will be 32: 8 padding bits and 24 bits for the RGB info. > > The padding bits are set to zero and this can be a problem if the pixel > > data is applyied in a ARGB context (A=alpha channel; if 0 then pixel is > > fully transparent, if 255 it is fully opaque). I have browsed the > > tightvncserver code hoping to find the place where I could change the > > value of these padding bits, but no luck so far. Does anyone know where I > > could do that ? > > It's not a good idea to change padding bits in the server code. Instead, > you should interpret pixel data correctly in the viewer. Can you explain why it's not a good idea ? Doing the correct interpretation in the viewer is the first thing I have tried, but the viewer is running in a very low ressources context so it's slow. That's why I would like to spare this interpretation on the viewer side by forcing the server to send the "correct" data. Loris |