-
-
Notifications
You must be signed in to change notification settings - Fork 278
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
Modernize Transfers-window #15885
Comments
Will this also finally enable a way to introduce a dark mode? |
Adding a single dark-mode aware window to Cyberduck won't make much sense. Besides, the targeted framework for this window won't magically enable dark-mode as it's been released back in 2006, and Microsoft never spent any time backporting Windows platform features back to it, but invented new UI frameworks. |
This was referenced May 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is an ongoing effort to improve the resource usage of Cyberduck on Windows.
Addresses:
In switching the UI stack from WinForms (currently) to WPF, we gain the ability to reduce our resource usage dramatically, by not requiring a window handle for each and every single control in the transfers window.
Instead there is only one window handle allocated for the entire window, everything else is done in software.
A welcome side-effect of this is the offload of rendering to the GPU, reducing the software-rendering requirements of WinForms.
With this, the foundation (controller-architecture) is switching to a view-model based approach, allowing an easier transition to another UI framework in the future.
WPF Limitations as outlined in #13036 apply.
Workaround
The text was updated successfully, but these errors were encountered: