You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just a tiny frustration: When both a supported (e.g. Nova) and a non-supported (e.g. Pixel) launcher are installed, the "Apply CandyBar Dev" button opens the launcher menu, even though the user actually has no choice:
Expected behaviour: The logic should be changed so that only supported launchers are considered when making the decision whether or not to apply icons immediately.
The text was updated successfully, but these errors were encountered:
I can see how this might actually be debatable. I'd be fine with contributing logic to auto-apply icons if the currently enabled launcher[1] supports icon packs. If this is also considered problematic, it could instead be hidden behind a switch in the dashboard-configuration XML which defaults to the current behaviour but lets icon devs opt-in.
Just a tiny frustration: When both a supported (e.g. Nova) and a non-supported (e.g. Pixel) launcher are installed, the "Apply CandyBar Dev" button opens the launcher menu, even though the user actually has no choice:
Expected behaviour: The logic should be changed so that only supported launchers are considered when making the decision whether or not to apply icons immediately.
The text was updated successfully, but these errors were encountered: