Replies: 7 comments 9 replies
-
@Donnnno FYI, curious what you think about this. |
Beta Was this translation helpful? Give feedback.
-
Implementation: #134 |
Beta Was this translation helpful? Give feedback.
-
Yeah, this is good. I didn't really think much while implementing this feature. Thanks for addressing the issue. |
Beta Was this translation helpful? Give feedback.
-
I use the current implementation to filter out piracy apps. Many apps can be identified thanks to the "start by" approach. Keeping the related apps in the list with the addition of an explanation is indeed a good idea. Thank you! Note: I think a quick how-to guide would be appreciated for such new features. I'm afraid several icon creators won't know how to use them (e.g. the recent PR for analytics). |
Beta Was this translation helpful? Give feedback.
-
So i'm implementing this in my packs right now and was wondering where the text stuff goes with the standard webapk stuff: |
Beta Was this translation helpful? Give feedback.
-
I have a force close when opening the icon request screen (I upgraded to 3.17.4).
What's wrong? |
Beta Was this translation helpful? Give feedback.
-
Was implemented with #134. Examples can be found in the comments above:
|
Beta Was this translation helpful? Give feedback.
-
@sarsamurmu thanks a lot for implementing #123, much appreciated! From what I see, the new filter sits in the place that detects the installed apps:
candybar/library/src/main/java/candybar/lib/tasks/IconRequestTask.java
Lines 113 to 114 in 529a761
Personally, I'd prefer icons to still be listed in the icon request section even if a filter is applied, but maybe greyed out, and display a reason to the user why they can't request it. Otherwise it's easy to look like a bug to the user and cause frustration.
Would you be open to such a contribution?
I'd keep the current interface intact and keep using the
true/false
return value offilterRequest()
to signify whether the app should be filtered out "hard", i.e. be made invisible. The implementation I have in mind would add two variables to theRequest
class:boolean isAvailableForRequest
(defaulttrue
, can be written fromFilterRequestHandler
)String infoText
(default''
, can be written fromFilterRequestHandler
)Covering these use-cases:
filterRequest()=false
--> not displayedfilterRequest()=true
andisAvailableForRequest=false
--> displayed but greyed outisAvailableForRequest=false
andinfoText='Web apps cannot be requested'
--> greyed out with infoisAvailableForRequest=true
andinfoText='App not listed on GooglePlay'
--> displayed with infoSome screenshots for demo purposes. They use the proposed implementation and the following code:
Beta Was this translation helpful? Give feedback.
All reactions