Is there a way to get what the workspace r~N gets resolved to using hyprctl/sockets?

[code-IM-perfect]

On the Dispachers wiki page (workspaces section), I came across the workspace selection syntax r~4 that enables me to select the 4th workspace on my current monitor, respecting the numbering of empty workspaces, which enables me to use workspaces exactly like I wanted (like they were implemented in AwesomeWM).

I want to make a workspaces widget in Quickshell but their API seems to give me a list of workspaces exactly like hyprctl workspaces gives me, and the numbering seems completely random to me, I cannot figure out any pattern in the IDs that would indicate exactly which workspace number in the r~ sense it belongs to.

So either there is some rule that hyprland uses to determine the id that goes to X monitor's Yth workspace or there is some info that hyprctl does not expose.

Is there a way to get this info via hyprctl somehow or maybe the exposed sockets?

[vaxerski]

not really

hyprland just counts from 1 up really, if it's not taken or on the monitor, add 1, then when your counter is at desired, thats the workspace

[fufexan]

Can I also somehow get hyprctl or the socket (or some direct way via quickshell itself) to get the full list of workspaces, including empty ones?

I don't really think that's needed. You could create an array of length n (with n being the number of the last workspace, because they start from 1) and only populate the positions where workspaces exist.

[code-IM-perfect]

Yeah but I believe at some arbitrary point, I would not be able to determine which workspace belongs to which number because the empty workspaces are also to be taken into account.

Like when there is content on id=7, then r~7 would translate to the next free workspace, say id=8, and r~8 translates to id=9. But even when the workspaces at id=8 and id=9 are cleared, switching to r~8 still moves me to id=9, even though id=8 is not occupied or on a different monitor.

So clearly hyprland is maintaining an internal list of empty workspaces too, which is essential to reliably predict what r~N translates to even for hyprland.

[code-IM-perfect]

@vaxerski Sorry for tagging you but I'm getting a bit confused here, if id=7 is on some other monitor, and id=8 is on the current monitor, wouldn't r~7 AND r~8 both resolve to id=8? How does hyprland know what id=8 was initially designed to?

Can you point me to the piece of code that dictates this logic?

And is there a way I could communicate to hyprland itself to check what each r~n is assigned to?

Alternatively is there a way I could directly go to (monitor_id * 10) + N instead of r~n? Cuz even though r~N works absolutely perfectly in my case and I prefer it cuz it works better if you wanna frequently disconnect with the secondary monitor, the second approach would greatly simplify my implementation on quickshell (I am trying to avoid plugins tho)

[vaxerski]

Can you point me to the piece of code that dictates this logic?

at an airport rn but search for workspaceidfromstring iirc (miscfunctions.cpp IIRC?)

[code-IM-perfect]

Ah yes, you're right, it's getWorkspaceIDNameFromString in MiscFunctions.cpp itself

Thanks!