

- QUORRABOT MUSICPLAYER CURRENT SONG FILE NOT UPDATING CODE
- QUORRABOT MUSICPLAYER CURRENT SONG FILE NOT UPDATING PLUS
Obviously this is ugly looking and hard to read, so we split the value to eliminate that text from displaying. Without this block, we'd end up with a song title such as Sound%20Of%20Pulling%20Heaven%20Down, a particular favorite song of mine by Blue October.
/do0bihdskp9dy.cloudfront.net/07-22-2022/t_be88440965154a969f66ba87ef9c7ad8_name_file_1280x720_2000_v3_1_.jpg)
This combination of characters represents a space in URL encoding, like what you could expect to see in a hyperlink address for a webpage. Also, we've got a split block in there, with a value to split at set for %20. Since our DataURI is 21 characters long and the extension including the period is 4 characters long, we take the total of those numbers (25) and subtract it from the total length of the Player source to get just the name of the song that is currently playing. The reason for this number is because when setting up the program, we don't know what songs will be selected, or how many digits in the title, but we don't want to display the entire source or the extension of the song, since neither of these two properties are relevant for the user. Next, we tell it to count for length of Player.Source minus 25.
QUORRABOT MUSICPLAYER CURRENT SONG FILE NOT UPDATING PLUS
Now, we are segmenting our text at the length of our DataURI (21 characters) plus 1, because we want to start at the first letter of the song. If you recall the properties we set for the ActivityStarter, we told it to start the activity at file:///sdcard/Music/, which just so happens to have 21 characters in it's string. Notice the length blocks used in conjunction with ActivityStarter.DataURI and Player1.Source blocks. Drag it's event block onto the Editor canvas, and set the blocks like you see in the picture on the left. Next will be the displa圜urrentSong procedure. You might be wondering what the displayPlaylistsprocedure does, which we'll get to next. Since there's no current playlist tosave, it disables that button and clears the current playlist label. Next it sets the playlists as the elements of our listpicker and enables the listpicker for displaying them. It checks the playlist, which will reset the button state to false, then it adds the tagDB to the other list, tinyDBTags, loads that list into the TinyDB, then displays the list of saved playlists to a label. Once the application loads that information, the whole procedure runs, which first saves that response as a tag to the TinyDB, then resets the list of songs to empty, and resets our play counter back to one for the next playlist the user sets up. It takes the response from the Notifier and loads it as the argument of this procedure: tagDB. Let me explain what this procedure does, from top to bottom: This procedure is called from our Save button and Notifier elements, which we'll get into later. Place the blocks according to the picture to the left.
QUORRABOT MUSICPLAYER CURRENT SONG FILE NOT UPDATING CODE
We're now going to code a fairly complex procedure, savePlaylist.
