tigervnc.git - High performance, multi-platform VNC client and server: https://github.com/TigerVNC/tigervnc

	Commit message (Collapse)	Author	Age	Files	Lines
*	Move computeScreenLayout/setScreenLayout to unixcommon lib	Peter Åstrand (astrand)	2018-04-09	1	-251/+0
\| \| \| \| \| \|	These two code blocks are not specific to Xvnc/vnc.so, but useful for x0vncserver as well. RandrGlue.h defines the interface on which unixcommon depends on.
*	vncRandRGetOutputName: return a copy of the string	Peter Åstrand (astrand)	2018-04-09	1	-3/+4
\| \| \| \| \|	Compatibility with libXrandr, where the name is in dynamically allocated XRROutputInfo.
*	Make vncRandRGetOutputId return the actual id; not a pointer	Peter Åstrand (astrand)	2018-04-09	1	-2/+2
\| \| \| \|	Less confusing, and compatible with libXrandr.
*	Adjust dimensions for rotated monitors	Pierre Ossman	2017-12-07	1	-0/+10
\| \| \| \| \|	We need to flip the dimensions in the case the monitor is rotated 90° or they won't map correctly to the framebuffer.
*	Call FatalError on fatal exceptions	Pierre Ossman	2017-12-07	1	-0/+12
\|
*	Adjust client pointer coordinates to absolute	Pierre Ossman	2016-08-18	1	-0/+10
\| \| \| \| \| \|	The client is not aware of where the screen is placed so it will give us screen relative coordinates. Convert to and from these and absolute coordinates before interacting with the input layer.
*	Set user/client requested mode as preferred	Pierre Ossman	2015-07-30	1	-28/+4
\| \| \| \| \| \| \| \| \| \|	Desktop environments like to change to the monitor's preferred mode, especially at login. Lacking one, they pick the highest resolution they can find. This tends to override what the user has picked, so try to work around the desktop environments by setting the preferred mode to what the user has chosen. Credit goes to Michal Srb who figured out the problem.
*	Use proper prototypes in headers for all our internal functions	Pierre Ossman	2015-01-29	1	-4/+0
\|
*	Restructure Xvnc/libvnc.so code to avoid C++ header hacks	Pierre Ossman	2015-01-26	1	-0/+362
	The internal Xorg headers are very incompatible with C++ and we've had to resort to all kinds of hacks in order to include them in our C++ code. This approach isn't really viable long term so restructure things so that we have a glue layer written in C that bridges the Xorg core with the RFB classes.