Tue, 10 Dec 2024 07:40:43 +0000 (UTC) Robert Webb via openSUSE Users <users@lists.opensuse.org> :
On Sat, 7 Dec 2024 08:40:20 -0500, bent fender <slowroller@trixtar.org> wrote:
Sat, 7 Dec 2024 06:27:27 +0000 (UTC) Robert Webb via openSUSE Users <users@lists.opensuse.org> :
On Fri, 6 Dec 2024 20:57:37 -0500, bent fender <slowroller@trixtar.org> wrote:
The residual part of the problem is that splashma-6 slews everything that would violate the deskbars margins even where there is no deskbar so I end up with this weird result:
If I do the ~/.profile call instead of kde-autostart then plasma is faced with a fait-accompli and the left eyes are exactyly where intended but I don't know how to trick the right eyes to go so much off the lo-res screen that they'll be just right in the hi-res final.
There is one which you can add (download) from the Add Widgets menu, 'Cursor Eyes'. [1]
[1] https://github.com/luisbocanegra/plasma-cursor-eyes/blob/main/README.md
Didn't know about that widget but I stay away from 3rd party addons as much as I can, not sure if that's a kde component per-se or not (but I will look at it). As far as I'm concerned 'xeyes' exists as it has for a very long time and all you need it a drop-in to some autostart foldet OR a ~/.profile call so that it might work exactly the the same way in any of my installed systems and regardless of the desktop being used. THAT is still THE Linux way. XCFE did the same thing, insread of ACCOMODATING an existing and perfectly adequate applet they too cooked up one that works only in XFCE, puke.
Reasonable viewpoint. OK, so I experimented with other ways of invoking xeyes.
Nothing wrong with that, I didn't mean to throw any pebbles :-)
Your call from ~/.profile happened too early; the screen resolution wasn't set yet.
OK, but it was never a problem before
The call from Autostart, after the window manager (Plasma) was in control, would not allow placement in the deskbar panels. But, there is a script file, ~/.xprofile, that, if it exists, is meant to be invoked during X initialization before the window manager is started. You would put the xeyes commands into that.
Some display managers will automatically source ~/.xprofile [2], but on openSUSE Tumbleweed, sddm does not. So, as suggested by that reference, I created, not the full xinitrc, but just an xinitrc drop-in script [3] to source it.
With the xeyes commands in ~/.xprofile [4], logging in at first showed the eyes near the edge of an otherwise blank screen, but a moment later, when the KDE desktop was displayed, the eyes were moved to just touching the panel, but not overlapping it. So the end result is the same as you had with Autostart. The display manager was able to move the xeyes out of the way even though they were started before the manager.
So this experiment was a fail, but I am attaching the two scripts [3] [4] so you may try them. Maybe some modification will make them useful. In any case, ~/.xprofile would be an appropriate place to put other per user X initialization commands. The scripts include logging, which you can view with:
journalctl -t xinit -b
I missed your comments about .xprofile, sounds interesting
Instead of a hack like this, what you need is a general wrapper command that would place a GUI app (like xeyes, or well, xclock) in the panel region of KDE Plasma.
I began with xeyes in XFCE where the widget went nicely into their panel but after kde had forced me to place it between deskbars as in this 'buntu-studio desktop I once had https://imgur.com/screenshot-1swkolq I actually got to like this placement better ... leering like like a moray eel from among cracks in the coral :-))
[2] https://wiki.archlinux.org/title/Xprofile [3] /etc/X11/xinit/xinitrc.d/10-source_xprofile (attached) [4] ~/.xprofile (attached)
-- Robert Webb
Swamped right now, looking for an EATX taichi white mobo at _my_ price...