On Fri, 6 Dec 2024 20:57:37 -0500, bent fender <slowroller@trixtar.org> wrote:
The 'disable' routine was useful because it allowed me to isolate i.e. to know that the call in ~/.profile is in fact *the first* execution. Once I took that out with your script and the dummy 'touch' file the second execution continued. I looked at
.config/autostart/
and there was a file I had earlier renamed to
was-my-xeyes-launch.bsh
forgetting the fact that the name of files in this folder doesn't make any difference. So I deleted it. Then I took out the dummy 'touched' file and sure enough I got the first set of eyeballs but since that takes place in lo-res they end up being in the left half-screen at 1920x1080.
The double execution had probably been going on for many months _unnoticed_ because the low-res screen never existed so second set just covered the first set exactly. When the lo-res screen began showing up (for whatever reason) is when three pairs became visible.
Interesting results.
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.
So Autostart is the right place to put xeyes start (desktop is set up in the final resolution), but then their placement fails because of Plasma desktop rules. That sucks. So what about instead using a Plasma applet, widget, plasmoid, or whatever they are called? One that could be within the panels (deskbars). There is one which you can add (download) from the Add Widgets menu, 'Cursor Eyes'. [1]
Anyway, the short of the long is that your suggestion to look in autostart was the key! Thanks.
[1] https://github.com/luisbocanegra/plasma-cursor-eyes/blob/main/README.md -- Robert Webb