-
Notifications
You must be signed in to change notification settings - Fork 202
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
Reveal effect for settings menu #167
Comments
Tentatively adding this to the 0.8.2 release, especially as 0.8.X is focusing on the settings menu. |
Well reveal and in-app acrylic are completely possible. These could be easily added 😄 |
Is there honestly a point? Microsoft will probably be ditching it because FluentUI for React doesn't have it, which they're increasingly switching, and adapting, to. |
doesn't mean it doesn't look great. |
Fuck it, G A Y flyout! /s Enough joking. Let me get on topic. I guess applying reveal to the buttons in the top bar would be too distracting. |
I was actually only thinking of the settings menu (navigation bar), for exactly this reason. |
Also The reveal affect should be on the buttons themselves not the flyout border as shown by the GIF |
Ok half the work done! Reveal Border Effect has been implemented in cd3652f. (still has some complications. will fix it later) Even though I found an easy way to add acrylic effect to our app, we shouldn't do that until #32 is fixed. |
Ok, will remove Acrylic from the 0.8.5 release. |
v0.10 is max timeline. We should try to fix #32 before v0.9. Don't add it to any projects because I'm still inconclusive of the solution. Let me ask aΔx before coming to a conclusion. |
We did it bois! After a series of 4 commits, Reveal effect is finally implemented properly. I will decouple these in the next release and move them to the ModernWpfCommunityToolkit so that other apps can be benefitted too. P.S.Bruh, it took me 5 hrs to get the exact same effect as in WinUI. RIP UI designers. Now I understand their pain. Oopsie.... |
Could we release v0.8.5 now? Whatcha say? Also I didn't even get the v0.8.2 update! I'm still stuck with the v0.8.1 build! Do something! |
Well-done @ShankarBUS,
How large is it? |
it's up to you |
Answer this #167 (comment) |
I guess it can be made into an option. It would be great! |
@ShankarBUS ahahahah! I see you saw my cheeky edit!! btw i've seen you on the unigram telegram channel. would love to talk to you guys about stuff outside of this repo!! |
Oh the collapsible
@Cyberdroid1 and I had a beef so we had to clear it up there.
You can contact me personally on Discord (ShankarBUS#3086) or Telegram (https://t.me/ShankarBUS). We also have a internal discord group (me, @Samuel12321 and @Cyberdroid1). You can join us there. You can also connect with other users of ours. |
Heya @Poopooracoocoo ! Join the telegram channel/discord server! We don't have any way to contact you! |
sure if you want, only question is whether we wanted to add a button for rainbow reveal and the Chinese localisation issue.
I personally think (as long as there isn't too much work involved), that it may be best to do it now so the languages are defined and we don't have any duplicate translation work done.
That's strange, v0.8.4 (rebranded 0.8.2 due to annoying store issues) has been in the store for a while now. |
just changed title to reflect what still needs to be added. |
Ah comeon! I have to do that again 😤.
It could stay hidden. We can do something later.
Ok merge the PR. Remove zh-CN and zh-TW resources. Imma add the remap. We bout to release v0.8.5.
Whooooooo, Azure pipelines releasing builds to store? Wouldn't that require "💲💰💵💸 M O N E Y 💲💰💵💸"????? |
Microsoft has removed reveal effects from WinUI 2.6 preview so I recommend not to add reveal to be consistent with other Windows apps in the future. |
i dont care rgb reveal is cool |
De-prioritized for now. This would be a post winui 3 thing |
So, reveal is officially dying now... Is it still worth to develop this anymore? |
As @JaiganeshKumaran & @Cyberdroid1 said, reveal is ded 💀. So, we should drop this 💀 |
Agreed, pity I quite liked reveal |
Just split this from #66 so each thread is specific to the feature.
The text was updated successfully, but these errors were encountered: