Is it still the case the AI Components cannot have input values that are defined by single value relations?
I was playing around trying to replace the Glide buttons in this screen with custom AI user interface buttons. However, the value is in a different table to the screen table, hence a relation is used to define the value that is being incremented/decremented. Seems like the AI components cannot manage this yet… is that true?
Update: I modified the screen table to point to the table where the hydration value is stored and applied a filter to the screen data (row date is within today’s date)… this avoided the need to use a relation. The screen is now looking nice…
Nice design!
Thanks… I added a transparent Gif of little bubbles continuously rising as an overlay to the container background image (water)… the GIF’s visibility controlled by the hydration amount so that when they reach the target 2000ml the water gently fizzes as a little reward. Kind of cute!
