If you give a Screen a width_transition and then update its width, it'll break after calling Application:child_value_changed( Screen ) which in turn calls QueryTracker:update( "child-changed", Screen ) which in turn will test the query function on the Screen which can break if the query is a tag query.
Solution: make Screen extend Sheet and define custom behaviour. They're pretty similar anyway, and then it'll be easier to target them in dynamic values later on. This will allow giving Screens tags and IDs. Nifty, huh?
If you give a
Screenawidth_transitionand then update its width, it'll break after callingApplication:child_value_changed( Screen )which in turn callsQueryTracker:update( "child-changed", Screen )which in turn will test the query function on theScreenwhich can break if the query is a tag query.Solution: make
ScreenextendSheetand define custom behaviour. They're pretty similar anyway, and then it'll be easier to target them in dynamic values later on. This will allow givingScreens tags and IDs. Nifty, huh?