On Thu, 26 Feb 2009 13:40:15 +0100
Adam Tkac wrote:
> On Thu, Feb 26, 2009 at 12:49:58PM +0100, Pierre Ossman wrote:
> >
> > The problem is that the code is very macro happy, so a basic profiler
> > will not easily tell you where the cycles are spent. If you dig a bit
> > more you'll see that th
This seems to be a style inherited from RealVNC. As such, any major
cleanup will mean that vendor drops won't be as easy when it comes to
the encoder/decoder parts. Is this still okay with everyone?
Ok with me.
Regards,
---
Peter Åstrand ThinLinc Chief Developer
Cendio AB
On Thu, 5 Mar 2009 15:07:33 +0100 (CET)
Peter Åstrand wrote:
>
> >This seems to be a style inherited from RealVNC. As such, any major
> >cleanup will mean that vendor drops won't be as easy when it comes to
> >the encoder/decoder parts. Is this still okay with everyone?
>
> Ok with me.
>
That
The server current selects a 16 bit framebuffer by default. I vote we
change this to 24-bit for the following reasons:
- It's what everyone else uses on their desktops and is therefore the
most tested method. We here at Cendio have already noticed a series
of annoying compatibility problems
On Thu, 5 Mar 2009, Pierre Ossman wrote:
>
> The downside to this is a potential increase in bandwidth. I'm not sure
> there is one in practice though.
It's not clear to me how the choice would affect network bandwidth
usage because the vnc client normally selects the bpp and depth, right?
Karl
On Thu, 05 Mar 2009 10:13:40 -0500
"Karl J. Runge" wrote:
> On Thu, 5 Mar 2009, Pierre Ossman wrote:
> >
> > The downside to this is a potential increase in bandwidth. I'm not sure
> > there is one in practice though.
>
> It's not clear to me how the choice would affect network bandwidth
> usa
On Thu, 5 Mar 2009, Pierre Ossman wrote:
> On Thu, 05 Mar 2009 10:13:40 -0500
> > It's not clear to me how the choice would affect network bandwidth
> > usage because the vnc client normally selects the bpp and depth, right?
>
> Silly me. You're of course correct.
BTW, I think your desire to cha
On Thu, 5 Mar 2009, Karl J. Runge wrote:
I wonder why the Xvnc default was set to 16bpp? Do you know if Realvnc
does this or is it a Tightvnc change?
VFB_DEFAULT_DEPTH is defined as 16 in xvnc.cc. It seems it has been
defined as 16 in all RealVNC 4.X versions, see:
http://tigervnc.svn.sour
Pierre Ossman wrote:
> The server current selects a 16 bit framebuffer by default. I vote we
> change this to 24-bit for the following reasons:
>
> - It's what everyone else uses on their desktops and is therefore the
>most tested method. We here at Cendio have already noticed a series
>o
