-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ref: Accept client-side wayland connection, global #8
Conversation
Signed-off-by: Shinyzenith <[email protected]>
// this anymore | ||
|
||
let mut state = state::WaysipState::new(kind); | ||
pub fn get_area( |
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 think the origin api should be reserved.Sometimes I do not want to induce wayland-client
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.
maybe add like get_area_with_connection
like this kind , maybe add one extra function will be better I think.
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.
or make connection and globals optional I think will be better. if it is none, make a new connection and globals
like create a struct
WaysipWaylandInfo<'a> {
globals: GlobalList,
connection: &'a Connection
}
I would perfer like this |
Looks good, would you want me to merge your pr or edit it into mine? |
Maybe committing to my branch |
ok, if that pr is ok, can you merge mime? |
sure |
Clients should be able to provide their own connection and global list instead of wasting time on another roundtrip / causing a segfault due to two open wayland-connections