Hi. I have a doubt with messages and maybe someone can help me.

Imagine I have got something like this:

[stdbuf -o0 xinput test 1(
|
[shell]
|
[set $1(
|
[a[1]=400(

It shows my x/y mouse coordinates I received from xinput using [shell] on linux.
a[0]=x and a[1]=y
So, sometimes I receive (the numbers are only examples) "[a[1]=400(" and another "[a[0]=400("
Is there any way for separate those two x y values from that final message?
For to be more specific I want extract x y coordinates (only the numbers) from that message.
Edit: I have simplify the patch, it was some convoluted.
Thanks a lot!

Hi,

I never used stdbuf before and the command stdbuf -o0 xinput test 1 isn't working on my system (it gives me unable to find device '1', but here are two ideas: if you need to work with x and y mouse coordinates, you can use [MouseState]. Alternatively, if you want to work with your patch above, you will probably need to do some kind of routing, so when the input is a[0]=something will go through one outlet, and a[1]=something will go through another one.

Take care,
Gilberto

Yes sorry, you must first find your device number running xinput on the terminal and the change it on the patch.
The problem with [MouseState] is that when you are on the limit on the screen then stop sending information even if you are moving the mouse. I want this for make something a rotary encoder pot with the mouse.
And there is also [hid], but it fails, it continues repeating bangs even if the mouse is stopped when showing the relative mouse position.
A solution for that [hid] problem is compare the xinput bangs with [hid] bangs.
But If I want xinput (If I'm not wrong with my test) is because you can disable the mouse on the screen (you can move mouse but no the cursor) but anyway you can receive the xy from that mouse anyway.
So you could have two independent mouses for work with pd.
How can I route that message to only numbers? I have been doing some test with no success...
Thanks Gilberto!

Oh, I see. So try this:

routing.pd

It seems to work, although this may not be the most elegant solution in the world.

Hope this helps, take care,
Gilberto

EDIT: 14 was the device number in my computer, so remember to change it back to 1 in your case

That is!
Thanks Gilberto, you are a master.
I add the same patch with a "rotary encoder" simulation, maybe can be useful for somebody.
It works with the "y" coordinates (if needed add another for the "x") and you must change the expr object.
Change it according to your screen size, on the example shows "899" because I'm working with a 1600x900 screen.
Sure the encoder can be done better.
Anyway like real encoders, if you go fast it would not work properly. Better for slow or smooth works with the mouse.
routing_2.pd