Adam Skelton

In one of my own apps, I have a Clipper with the same shape as an underlying Container. I still wanted the Border to match, but I ended up reducing...

I have never personally experienced this visual bug when using this package, but I also use bespoke styled objects for each portion of the [SlidingSheet], i.e. my [SlidingSheet.headerBuilder] returns a...

> I deleted my comment because I saw that the web demo was working fine. So I thought of try running the example first. > I don't know what I'm...

I have an extremely limited knowledge of iOS and as such the testing for that platform was less than thorough. If I take another look, it may be as simple...

I have finally sat down to look into this. It seems like it may be a simple fix. We are after [this value](https://developer.apple.com/documentation/coremotion/cmdevicemotion/1616140-magneticfield), the *calibrated* `magneticField` property of a [`CMDeviceMotion`](https://developer.apple.com/documentation/coremotion/cmdevicemotion)...

> Just FYI, in the meantime, I've used this library: https://pub.dev/packages/motion_sensors and it seems to have a proper implementation. I remember when I was building a sensors based package I...

Barring a check for availability of sensors and providing a means to alter temporal accuracy, this implementation should accomplish the same expected functionality as from `motion_sensors`: ```objective-c @implementation FLTMagnetometerStreamHandlerPlus -...

I wish I had an iOS device to verify this fix. Could be checked by someone else if they have the time: ```yaml dependencies # Testing calibrated magnetometer on iOS...

> @Zabadam Thanks for your effort! > > I just used this dependency and it seems that it's still showing higher values than the other apps or the `motion_plus` package....

The PR that implements this fix will likely soon be merged. As the code is technically correct, especially when compared to your other linked package that implements iOS magnetometer support,...