-
Notifications
You must be signed in to change notification settings - Fork 32
Make a new wayland backend using smithay-client-toolkit #107
Conversation
loop_signal: LoopSignal, | ||
pub(super) idle_sender: Sender<IdleAction>, | ||
pub(super) loop_sender: channel::Sender<ActiveAction>, | ||
pub(super) raw_display_handle: *mut c_void, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could keep the Connection
around for this or get the underlying Backend
from wayland-backend and keep that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would like to avoid random 'Application' instances keeping the connection alive(?) without reason, which it's possible that this would do.
But I'm not tied to this particular implementation decision
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a good start. This looks good to merge once PR #117 is merged.
Previous commit histories can be found in waylander and waylandest. Those histories were abandoned to rebase over #103, #104 and #105.
Works towards #28
Future work, which should probably be done before merge
Other future work, which can be collaborated on once merged:
OutputState
, I thinkWhat do we actually use monitors for?