"TheEndless" wrote:
These questions are all easily tested, so to quote another helpful forum member.. have you tried it? 😉
Touché!
😄Not quite... but
touché, Sir - for digging these examples!
Here is what i mean by "not quite". There could be different standards on documentation - personally i would be satisfied by one that a "
competent and reasonable developer" can read and use. By "reasonable" i mean "a hypothetical person in society who exercises average care, skill, and judgment in conduct" (see
Reasonable Person Standard). And by "competent developer" i assume one that knows the difference between between a local and a global variable, between a value and a reference type... actually pretty high bar, comparatively to what we get in Roku world.
To which i posit, such competent&reasonable developer:
- reading that Overhand is subclass of Group, will deduce children can be added
- will expect 4k video plays like any other, in the absence of explicit disclaimer
- will expect "any callback functions or message ports" for unobserveField() to mean the "nuclear option" (everywhere in the app)... and will be wrong on that, per your experiments
So this is an
under-documented or wrongly-documented behavior that should be fixed - otherwise
unobserveField() is useless, without it being codified whether it affects the other xml-components or not.
