-
Notifications
You must be signed in to change notification settings - Fork 556
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
Expose more window API #333
Labels
Comments
tronical
added a commit
that referenced
this issue
Jul 20, 2021
If we were to add `sixtyfps::window::Window` to the re_exports, then this clashes. We might rename the former, but this is a cleaner naming in any case. Relates to #333
tronical
added a commit
that referenced
this issue
Jul 20, 2021
If we were to add `sixtyfps::window::Window` to the re_exports, then this clashes. We might rename the former, but this is a cleaner naming in any case. Relates to #333
tronical
added a commit
that referenced
this issue
Jul 20, 2021
If we were to add `sixtyfps::window::Window` to the re_exports, then this clashes. We might rename the former, but this is a cleaner naming in any case. Relates to #333
tronical
added a commit
that referenced
this issue
Jul 22, 2021
The generated component now provides access to a Window type via the window() accessor function. This is part of #333
tronical
added a commit
that referenced
this issue
Jul 22, 2021
The generated component now provides access to a Window type via the window() accessor function. This is part of #333
tronical
added a commit
that referenced
this issue
Jul 26, 2021
The generated component now provides access to a Window type via the window() accessor function. This is part of #333
tronical
added a commit
that referenced
this issue
Jul 26, 2021
The generated component now provides access to a Window type via the window() accessor function. This is part of #333
tronical
added a commit
that referenced
this issue
Aug 3, 2021
The generated component now provides access to a Window type via the window() accessor function. This is part of #333
|
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The slint::Window struct has a fairly limited API so far compared to what winit and other framework offer.
We should either duplicate most of their capabilities so it can be used from Rust/CPP/JavaScript/Python/...
Some features of the window that relates to the UI itself can be done on the .60
Window
element in a declarative way:title
property)The more imperative UI can be done via API:
One would need to expose what is currently the
ComponentWindow
into a publicsixtyfps::Window
which has function to do a bunch of things.This include:
The
items::Window
need to be renamedWindowItem
to avoid duplicated name (just likeImageItem
)The text was updated successfully, but these errors were encountered: