Kdesktop_lock widget positioning (KDE 3.5)

[Andrew Reid]

  Hi all --

  This is a bit of an aesthetic question.

  I run Debian "etch" with KDE 3.5, and have recently set up
a dual-monitor set-up, with the desktop spread out over two
monitors.  It's an NVidia rig, using TwinView, and it all
works fine.

  The issue is that, when I lock the screen, and then unlock
it, the unlocking widget is positioned in the center of the 
dual-monitor desktop, right smack on the "seam" between the
two monitors.

  I'd like to move this widget to the center of one of the
monitors.

  I found a setting for the KDM greeter, there's a 
"GreeterPos" setting in the "X-*-Greeter" section of 
/etc/kde3/kdm/kdmrc, which accepts percent-of-x-extent
and percent-of-y-extent arguments.  This is wonderful.

  Is there something similar for the desktop unlocking?

  What I have tried so far:

  - Searched high and low for a description of the allowed
settings (and their meanings) for the 
$KDE/share/config/kdesktop_lockrc file -- no luck so far.

  - Provided a standard X-style "-geometry" argument to the
kdesktop_lock on the command line -- this does nothing,
presumably because the lock application itself eats this argument,
and ignores it because it runs in the root window, and does
not pass it on to the unlocking widget, which in turn doesn't
see it because it's not the primary application.

  - Tried to get the window or app ID for the unlocking widget
with the goal of setting up XResources for it to try to position
it through the "back door" of the X server. My X-window-fu
is rather poor, the widget is transient, and this has not
yet worked.

  - Asked on Debian-User.  Sank without a ripple, which wasn't
surprising, it's a bit out of scope for them.

  Clues welcome.

				-- A.
-- 
Andrew Reid / reidac at bellatlantic.net
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.