vaivis has quit [Read error: Connection reset by peer]
Guest2536 has joined #river
Ghassan[m] has joined #river
Guest2536 has quit [Quit: Client closed]
uncomfy has joined #river
uncomfy has quit [Ping timeout: 265 seconds]
uncomfy has joined #river
waleee has quit [Ping timeout: 264 seconds]
snakedye has quit [Ping timeout: 255 seconds]
snakedye has joined #river
uncomfy has quit [Remote host closed the connection]
snakedye has quit [Read error: Connection reset by peer]
snakedye has joined #river
snakedye has quit [Ping timeout: 255 seconds]
snakedye has joined #river
nullndvoid has joined #river
adamcstephens has quit [Ping timeout: 240 seconds]
adamcstephens has joined #river
wrkzk has joined #river
tsraoien has quit [Quit: WeeChat 3.5]
tsraoien has joined #river
<nullndvoid>
I am using zriver_seat_status_v1_add_listener to get the active tag(s) in River, and I don't know what to pass to the void* data argument. I am using C.
<nullndvoid>
also I just realised I need the output version to get the currently focused tag, so thats a start I think?
hellmouth has joined #river
<leon-p>
nullndvoid: thats for user data. If you don't need to pass any, you can use NULL
<nullndvoid>
thank you, I just about worked it out when I am posting this, I looked at the waybar river module source code which was helpful for me anyway
<nullndvoid>
leon-p: sorry to ask, but what is user data? I see some functions to do with it
<leon-p>
nullndvoid: sometimes you need to access some other data in a handler, so it's common to have a struct containing all your programs context and pass a pointer of that as user data. For smaller projects, keeping all that global instead is sufficient though IMO.
wrkzk has quit [Quit: WeeChat 3.5]
<nullndvoid>
leon-p: thanks, that makes sense now.