Ydotoold, Virtual keyboard, is player 1

Arrafart

Armbian OS Gnome Ubuntu jammy v42.9
Device model : Orange Pi Zero 2W (aarch64)

Hi all,

I need to use ydotoold, Wayland, instead of xdotool and this sadly comes with a price. No matter what I do within the OS (already tried once to rebuild the .c file to destroy the keyboard functionality and keep the mouse (will try again)), Retropie puts the virtual keyboard as player 1.

... X ydotoold virtual device (9011/26214) not configured
... + Xbox Wireless Controller configured in port 2

Is there any way to identify the virtual keyboard, and ignore it, or otherwise place it as player 7, 8 or 9 from within RetroPie?

Alternatively (non Retropie related), a better way to launch the Desktop with the cursor in the bottom right corner?

Thanks!

mitu

@Arrafart said in Ydotoold, Virtual keyboard, is player 1:

Is there any way to identify the virtual keyboard, and ignore it, or otherwise place it as player 7, 8 or 9 from within RetroPie?

Yes, use the configuration editor and set it to P2, bringing the Xbox controller to P1.

Alternatively (non Retropie related), a better way to launch the Desktop with the cursor in the bottom right corner?

Not without a -tool to run, but why do you need this ?

Arrafart

@mitu

Thanks Mitu, I'll check the configuration editor tonight.

Not without a -tool to run, but why do you need this ?

I have autostart for Retropie and don't want to see the mouse in the terminal menus, I want to use the mouse only when I exit Retropie.

Arrafart

@mitu virtual keyboard is not shown, only Xbox controller. If I set Xbox to player 1, no impact on the virtual keyboard.

mitu

@Arrafart said in Ydotoold, Virtual keyboard, is player 1:

@mitu virtual keyboard is not shown, only Xbox controller. If I set Xbox to player 1, no impact on the virtual keyboard.

That's weird, since RetroArch does detect it as a gamepad. Can you post the outpu of the following command:

cat /proc/bus/input/devices

when both the controller and the virtual keyboard are on ?

BTW, if you're just using the tool just to move the mouse, is there any reason to leave it running in the background once it's done its job ?

Arrafart

@mitu

Can you post the output of the following command:
cat /proc/bus/input/devices
when both the controller and the virtual keyboard are on ?

I uninstalled all of ydotoold and ydotool and wanted to live with it, but ran N64 and the mouse was 100% visible.

I'll reinstall the bunch tomorrow.

BTW, if you're just using the tool just to move the mouse, is there any reason to leave it running in the background once it's done its job ?

Nope, don't need it. I tried to make the launching script turn off ydotoold, but I already needed a workaround to install the tool and chatgpt could not find its own installation paths and service files, so that failed XD. Hell of a time consuming job for me.

I'll try: cat /proc/bus/input/devices, and get back here. Will take a moment... Any further help/advice is appreciated 👍🏻

Arrafart

@mitu

BTW, if you're just using the tool just to move the mouse, is there any reason to leave it running in the background once it's done its job ?

FYI, so far so good, built ydotool with mousemover only with help from AI.

Hope it works XD

https://pastebin.com/sw6gDY5p

Arrafart

@mitu said in Ydotoold, Virtual keyboard, is player 1:

@Arrafart said in Ydotoold, Virtual keyboard, is player 1:

@mitu virtual keyboard is not shown, only Xbox controller. If I set Xbox to player 1, no impact on the virtual keyboard.

That's weird, since RetroArch does detect it as a gamepad. Can you post the outpu of the following command:
cat /proc/bus/input/devices
when both the controller and the virtual keyboard are on ?

I: Bus=0006 Vendor=2333 Product=6666 Version=0001
N: Name="ydotoold virtual device"
P: Phys=
S: Sysfs=/devices/virtual/input/input10
U: Uniq=
H: Handlers=sysrq kbd mouse1 event9 rfkill
B: PROP=0
B: EV=7
B: KEY=ffffffffff 0 ffffff0003007f 1000f7fffffff 7fe001fffff000f 7ffffffffffffff ffffffff0003fdff 7fff8fff00ff03ff 1ffffffffffff07 ffffffffffffffff ffffffffffefffff fffffffffffffffe
B: REL=147

I will ask AI in the meantime, hehe, staying in touch

Arrafart

@mitu Thanks for the hint to check the devices and whether I really need to keep it turned on.

I could build a script with the help of AI, maybe not the most efficient script, but it works XD

https://pastebin.com/rediyUG6

My Autolaunch for Emulationstation waits for this script to finish. They did not work together as 1 script.

Arrafart

FYI anyone reading.

I added a sleep 1 to the ydotool script at launch and a sleep 1.5 to my emulationstation auto launch script for a more stable result.