-
Notifications
You must be signed in to change notification settings - Fork 190
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
Any plan on releasing the v0.10? #1282
Comments
The people working on this project have not really done much for more than 6 months so I don't know if they're going to actually rewrite this project. |
I am the lead developer of ModernFlyouts. I dropped this project in 2021. My teammates are trying their best to keep this project alive. But we all have careers that are taking up too much of our time. I started this as a fun project for my personal use. I learnt a lot of things while developing it. We are really sorry for no progress and ample amount of unfixed bugs. I tried to port this to WinUI 3 (i.e. the thing that Windows 11 shell uses now). But transparency and acrylic still remain the hard part. It would take me a lot of time to rewrite the entire UI. Not just the rewrite but different behaviors between the UI frameworks would introduce new bugs. But to be fair, if I could get some free time, I will definitely do my best to get this project alive again because this is my first app that I published. |
I wouldn't mind helping out with this project. |
I am really glad you are willing to contribute to this project. If I am not wrong, you are the one who fixed the NativeFlyoutHandler to handle the Windows 11 flyouts and made another PR which is still open. I am really thankful for your contribution! I would like to have a conversation with you. And give you some guidance. How can I contact you? |
@ShankarBUS @manstheram best if we have a chat on discord. |
Description of the new feature / enhancement
According to the project page the main requirement has been merged.
I understand there is a major rewrite ongoing, but having a lot of bug-fixes only available in the release candidates for mouths now is a missed opportunity to keep new issues under control.
And given the plan for v0.11 (which looks great btw 😄), perhaps this would mark a good milestone before the next release.
Scenario when this would be used?
Helps to reduce new issues for already solved bugs.
Mark the great improvement between v0.9 and v0.11.
Additional context
No response
The text was updated successfully, but these errors were encountered: