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

Visible offline 2.0 #129

Merged
merged 6 commits into from
Jan 6, 2025
Merged

Visible offline 2.0 #129

merged 6 commits into from
Jan 6, 2025

Conversation

mattcarter11
Copy link
Contributor

  • centralize SongListItem logic
  • select header also consider connection

@mattcarter11 mattcarter11 force-pushed the visible-offline branch 3 times, most recently from cc883b8 to 3ad3895 Compare December 17, 2024 22:13
Copy link
Collaborator

@mikooomich mikooomich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The above

@mikooomich mikooomich merged commit 5809f53 into DD3Boh:dev Jan 6, 2025
1 check passed
@mikooomich
Copy link
Collaborator

History screen multi select doesn't work for disable songs, but it does for playlist. Is this intentional?

reocat pushed a commit to reocat/OuterTune that referenced this pull request Jan 6, 2025
* songs: centralize SongListItem logic + select header also consider connection

* songs: add play when offline logic (only play offline items)

* songs: fix song selection when offline

* app: Fix codestyle

* refactor: move select logic to parent
reocat pushed a commit to reocat/OuterTune that referenced this pull request Jan 6, 2025
* songs: centralize SongListItem logic + select header also consider connection

* songs: add play when offline logic (only play offline items)

* songs: fix song selection when offline

* app: Fix codestyle

* refactor: move select logic to parent
@mattcarter11
Copy link
Contributor Author

History screen multi select doesn't work for disable songs, but it does for playlist. Is this intentional?

What do you mean exacly? Multiselect in history should be like any other place. If a song is available (curently have connection or is downloaded) should be selectable.

@mikooomich
Copy link
Collaborator

I tested it again, and when offline it's not selectable across the board. I'm not sure if it's a issue after merging, however in it's current state, it's something like this

Screenshot_20250107-174752_OuterTune Debug.png

@mattcarter11
Copy link
Contributor Author

It's not a bug, it's intentional, because the actions you can do with songs don't work when offline (like, add to library, playlist, download, play ...)

reocat pushed a commit to reocat/OuterTune that referenced this pull request Jan 8, 2025
* songs: centralize SongListItem logic + select header also consider connection

* songs: add play when offline logic (only play offline items)

* songs: fix song selection when offline

* app: Fix codestyle

* refactor: move select logic to parent
@mikooomich
Copy link
Collaborator

Ah, ok. All good

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

Successfully merging this pull request may close these issues.

2 participants