region-management

Prism 7 throws and exception when working with nested views

浪尽此生 提交于 2021-02-05 08:14:14
问题 I posted similar question few months ago Working with nested views using Prism with IsNavigationTarget which can return false, I'm still not sure what is the proper way to do it. Imagine you have a view A, in this view A you have declared a region A, then you injected a view B into this region A. Similarly, in View B you have registered region B, and then you injected a view C into this region B. As it shown on the following picture: In the ViewModelA for ViewA, I have a method SetUpSubViews(

didEnterRegion works in foreground but not background or other VCs

限于喜欢 提交于 2019-11-29 02:19:19
If the app is running and the CLLocationManagerDelegate class is the foreground (i.e. visible) then the didEnterRegions triggers and I get both the NSLog as well as the AlertView. However, I get nothing when the app is in the background or, essentially, if the screen is showing anything but the delegate class. I have set "App registers for location updates" under "Required background modes" in the plist although I'm not sure that's even necessary. Here's what I think is the relevant code although I may be wrong (and will gladly add more). I should note that everything in viewDidLoad is wrapped

didEnterRegion works in foreground but not background or other VCs

余生颓废 提交于 2019-11-27 16:35:24
问题 If the app is running and the CLLocationManagerDelegate class is the foreground (i.e. visible) then the didEnterRegions triggers and I get both the NSLog as well as the AlertView. However, I get nothing when the app is in the background or, essentially, if the screen is showing anything but the delegate class. I have set "App registers for location updates" under "Required background modes" in the plist although I'm not sure that's even necessary. Here's what I think is the relevant code