Lars

I think I got it. I have to provide the "context" protocols as well ``` pywayland-scanner -i /usr/share/wayland/wayland.xml /usr/share/wayland-protocols/stable/xdg-shell/xdg-shell.xml wlr-layer-shell-unstable-v1.xml -o protocols ```

But now the imports in the generated files are not quite correct because the imports are now relative to each other and i.e. pywayland.protocol.wayland is not used. I suspect that...

Currently the above should require the following code: ```python for i in range(1, 33): try: display.add_socket(f'wayland-{i}') except (RuntimeError, Exception): continue # Maybe socket in use break ```

I ran into the same problem. Are there any plans to implement it? Almost all protocols, or at least the ones I am interested in, use ``new_id``

@flacjacket, I attempted to address this issue with PR #64 Unfortunately, I couldn't think of a more elegant way to get the required WlDisplay object, so I'm trying to do...

@flacjacket, thoughts on this? Or a better idea how to get access to the WlDisplay?

Are there any issues which have to be solved for a new release? Note that there is a newer version of wlroots (0.17.1)

Good point. I'd prefer properties unless we want to imply "costs" through a function call. Presumably the current approach is that there is a property if there is a ``wlr_X_get_Y``,...

One question I have is whether it makes sense from a Python developer's perspective to know whether a struct member is being accessed or a function is being called. Ultimately,...

> As written, I have a tendency to use properties for both read and write access, but I would also be open to any other solution as long as it...