Skip to content
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

chore: cleanups to allow List-based input of collection path #15784

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

david-allison
Copy link
Member

@david-allison david-allison commented Mar 5, 2024

onDisplayPreferenceDialog: If a call to super is requested, null may be returned In this case, super would be called

This is useful if you would optionally want to inherit from a class (say EditTextPreference), but also allow conditionally return a different fragment

  • Prep for Nicer way to enter path to put the collection #3114 :
    • We'll want a ListPreference if the user is on play
    • An EditTextPreference if the user is on full
    • Preferences screens don't expect two preferences for the same key
      • So we need one preference which will change implementations

One refactoring to CollectonManager


A new trait which allows a list preference to optionally be displayed when a preference is clicked

@david-allison david-allison changed the title chore: 'DialogFragmentProvider' - make optional chore: cleanups to allow optional input of collection path via List Mar 5, 2024
@david-allison david-allison force-pushed the 3114-select-storage-location branch 4 times, most recently from 0e96bdf to 55347e6 Compare March 5, 2024 20:39
@david-allison david-allison changed the title chore: cleanups to allow optional input of collection path via List chore: cleanups to allow List-based input of collection path Mar 21, 2024
If a call to super is requested, `null` may be returned
In this case, `super` would be called

This is useful if you would optionally want to inherit from
a class (say `EditTextPreference`), but also allow conditionally
return a different fragment
I know `getExternalFilesDir(null)!!` can throw, I'm unsure
if the array can throw, but it's best to be safe here
This exists as we want a dialog to show either a List or an EditText,
and both the framework classes require inheritance

For Issue 3114
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant