| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
| |
913fcf1a74426725f14380dd5b34286a21c37ab7.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Backported from X.org:
commit fd8bde8bb0f9d796b3464973b53285c0a6d22a31
Author: Daniel Stone <daniel@fooishbar.org>
Date: Mon May 29 11:14:03 2006 +0000
Remove -xkbmap argument.
Backported-to-NX-by: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
|
|
|
|
|
|
| |
* Support for XkbCF has been dropped in XKB extension by X.org
* Has never been used in recent NXv3 implementations (e.g. X2Go)
* Config file parsing is error prone, use setxkbmap API instead
|
| |
|
|
|
|
| |
so let's remove some superflous tests
|
|
|
|
| |
Just to be sure. It is used at lots of locations afterwards.
|
|
|
|
|
|
| |
Some of them have not been seen in the wild yet.
Partly fixes ArcticaProject/nx-libs#711
|
|
|
|
| |
as in xorg-xserver upstream's hw/xnest/Keyboard.c
|
|
|
|
| |
Fixes ArcticaProject/nx-libs#701
|
|
|
|
| |
Fixes ArcticaProject/nx-libs#694
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
nxagentHandleConfigureNotify() has an optimization that accumulates
ConfigureNotify events from the queue to only perform the changes of
the last ConfigureNotify event in the queue. But that code used to
ignore position changes and only adapt the new window position if the
last event happened to contain a position change.
This change ensures the latest position change - if any - found in the
queue will be applied after the accumulation.
Fixes: ArticaProject/nx-libs#688 (second part)
|
|
|
|
| |
Was 0,0 on every call...
|
| |
|
|
|
|
|
|
| |
This is the preferred way. It ensures, that
a) the data is zeroed
b) a correct size in case xlib is changing the size of the structure in future releases
|
| |
|
|
|
|
| |
nxagentSetWMNormalHints was slightly adapted therefore
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
if the output was disconnected before.
Fixes: ArcticaProject/nx-libs#677
|
|
|
|
| |
avoid referencing random data.
|
| |
|
|
|
|
| |
implemented in intersect_bb() function.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the agent window is moved around on screen, it can happen
that it is moved into an invisible area of the real Xserver,
we calls this "beyond the bounding box".
.
If the agent window is partially beyond the bounding box, we
don't want Xinerama to re-adjust the RandR parameters inside the
agent. Near the bounding box, the session shall stay intact.
.
This means, desktop env wise, the desktop session control
elements can be moved (with the agent window) into the invisible
areas of the real Xserver and moved out again without RandR
events arriving inside the agent session.
Fixes ArcticaProject/nx-libs#662.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Keeping it enabled leads to nxagent consuming 100% of CPU resources
after some time.
Older code used three different timers for each DPMS mode (standby,
suspend, off), with each timer checking that the elapsed idle time is
strictly less than the DPMS mode timeout value.
Newer code started merging DPMS and ScreenSaver timers into a single
one, with checking DPMS modes and timeouts in a fall-through fashion.
The code expects that, if a timeout is reached, the mode is set
accordingly, so that the old timeout is disregarded next time.
Since we stub out DPMSSetMode() in nxagent, this doesn't happen.
In this case, the old DPMS timeout will be checked the next time around
and we will be calculating DPMS_MODE_TIMEOUT - IDLE_TIME. If IDLE_TIME
is bigger than DPMS_MODE_TIMEOUT, we run into problems with unsigned
integers. What happens next will be *another* overflow once DoTimers()
is executed and from that function SetTimers(), which will add the
current timestamp to the timeout value. Later functions subtract the
current timestamp again (which will be even higher since some time
elapsed) and underflow the value again.
It looks like this leads to consistent firing of the timer - something
we do not want to have.
For new, disable DPMS support in nxagent. We do not execute it on actual
hardware that could change DPMS modes.
At a later time, implementing a DPMS timeout/mode passthrough to the
connected X server/display might be beneficial.
Fixes: ArcticaProject/nx-libs#671
|
|
|
|
|
|
| |
nothing better can be detected.
Fixes ArcticaProject/nx-libs#668.
|
| |
|
|
|
|
| |
is used nowhere anyway
|
|
|
|
|
| |
make them appear in the nx section. Also separate the nx section from the
other options by an extra emtpy line.
|
|
|
|
|
|
|
| |
In XORG-7_1 xkbconfig.c had been dropped. We must keep this file
because it is used by hw/nxagent/Keyboard.c to load the xkb
configuration file. Maybe we should move the relevant code to there or
drop xkb configuration file support from nxagent.
|
|
|
|
| |
only effect on session startups.
|
| |
|
|
|
|
| |
magicpixel takes a boolean argument for now.
|
|
|
|
|
|
| |
of file.
Fixes: ArcticaProject/nx-libs#664
|
|
|
|
| |
I left out glx changes to miinitext.c for now.
|
|
|
|
| |
'nxagentProgName' instead and pass it around where needed.
|
| |
|
|
|
|
| |
Fixes ArcticaProject/nx-libs#639
|
|
|
|
| |
Fixes ArcticaProject/nx-libs#653.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes ArcticaProject/nx-libs#657.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit c804d99f2c4ea21e37cc8f6c3168b7b79d0d721a.
It seems like the missing code was missing for a good reason. Including
it leads to very strange issues when coupled with libXcomp and using
connection speed settings lower than LAN (and even on LAN some icons
are not showing up correctly, e.g., when using MATE).
Further investigation on why this happens pending and might happen at a
later time.
Fixes: ArcticaProject/nx-libs#656
|