Kent Boogaart

@Hinidu yep, certainly an option worth considering.

See also: https://forums.xamarin.com/discussion/84510/proposal-improved-life-cycle-support

See also: https://forums.xamarin.com/discussion/84510/proposal-improved-life-cycle-support

@MelbourneDeveloper btw, the only recourse I have found is to forward life cycle events from the host page to any views within it that need to activate/deactivate. It's a bit...

FYI, the problem is actually in `ObservableForProperty`. It's not notifying in this scenario: ``` C# [Fact] public void NAME_THIS_SUCKER() { var fixture = new TestWhenAnyObsViewModel(); var output = fixture.ObservableForProperty(x =>...

Here's my best articulation of the problem based on some further research into this issue... In the example test in my previous post, when `fixture.Child` is set to `null`, the...

Reviewing this again, I think this is probably just down to the semantics of `WhenAny*` with respect to invalid property chains. By breaking the chain, it keeps ahold of the...

Following on from a Slack discussion today, it would be awesome if we could do this at compile time via Roslyn compile-time hooks. Alas, they do not support that yet,...

  This is the app I finished working up on recently. It connects to proprietary Bluetooth headwear that monitors your fatigue level, alerting you when configurable rules are triggered...

Another simple workaround would be your own widget, say `OptionallyAutoSizeText`, that wraps `AutoSizeText` or `Text` depending on the value of an additional `bool` field.