You’re not crazy. It’s not there just yet. You can make the changes to the dvl rows using loops or when you make the data. Want an example?
so for context. each user in the app has a list of notes. each item in the list is an object and each object has a handful of properties.
So i first delete all the rows in Table 1
then I get the list of objects stored under
cloudNoteBucket/firebaseUserID/notes/ and loop through it
during each loop, I create a new row in Table 1
- because each item in the list is an object, I use the ‘get property of object’ and use the variable j to extract a value to save for each column in the table
– j is a temporary variable in this loop. it’s used as a stand-in for each item in the list/array. so during the first. loop, j is the first item in the array, during the second loop it’s the second item, and so on.
for the image value column, i save either a true/false value
then after each row is created, i test if the CrossedOut Value for j = the word true or false and return a boolean true/false value.
- (it’s key to understand a word ‘true’ isnt the same as the green ‘true’ logic block or what this yellow block returns which is also a boolean value)
notice that when you save a row, it returns a green
rowID block. if j’s crossedOut is true, then i use that rowID to modify the corresponding DVL row. So when row 1 in Table 1 has a crossedOut value of true, then the DVL’s row 1’s components can be modified. in this example, i am showing/hiding 2 different labels.
the next if block sets an image in the DVL to be visible when there is an image to show and keeps the image element hidden when it’s not present! it uses the same logic.