Dear Darrell,
I am sorry, I did not mean to offend...
> ?? Not sure if I understand what you're trying to say. I spent many
> many hours improving the full-screen functionality in 1.1 beta (relative
> to 1.0.2.) Those hours were paid for by another user, so your company
> received that work fo
Dear List, dear Darrell,
after one day of extensive testing we have concluded that the
screensaver settings might be the cause of the problem (at least with
version 1.0.90 that we've installed now).
As soon as I had double-checked the screensaver and energy savings
settings and turned everything
On 3/12/12 9:03 AM, Andreas Delleske wrote:
> I am sorry, I did not mean to offend...
I'm not offended. I was just confused. Your message seemed to be
saying that you were threatening to drop TurboVNC if I didn't solve the
problem for you. I may have misunderstood what you were trying to say.
I am very curious to see if the grabKeyboard solution or using one of
the other viewers helps. The "full-screen fixes" in the TurboVNC 1.1
Unix Viewer amount to using a similar technique to FLTK (which TigerVNC
1.2 uses.) It involves basically notifying the window manager via a
special client mes
So far testing with TurboVNC 1.1beta on RHEL 5.6 looks good, I verified
it solves our OpenGL application's Qt 4 font problem on RHEL 5.6.
However, things aren't right using Xvnc servers that are compiled
on either OpenSuse 12.1 or CentOS 6.2.
On OpenSuse 12.1, it compiles without any errors, but
On 3/12/12 3:19 PM, Craig Ruff wrote:
> On OpenSuse 12.1, it compiles without any errors, but when started it
> complains about not finding the "fixed" font (which is defined the same
> way it is on CentOS 6.2 and RHEL 5.6 in .../misc/fonts.alias).
>
> I was able to get Xvnc to start by setting $f
