Hi :) I'm using BAFluidView with interface builder and autolayout, and I noticed a glitch when doing so:

http://d.pr/v/aR6

looks like the bezier path are computed at the starting size, but once autolayout resizes it to fit a bigger screen those values are no longer valid.

This sample shows the issue (you might need to hide the frontmost mask in IB, or just run it on your device and tilt it :) )

Any idea?

Thanks

Hey just want to let you know that doing just pod install on the Example folder triggered this error:

[!] Unable to satisfy the following requirements:

• BAFluidView (from../) required by Podfile
• BAFluidView (from../) required by Podfile
• BAFluidView (= 0.1.1) required by Podfile.lock

However, running pod update after solved it.

This should fix #14 although it might need to be documented in the readme since this happens also when you have a fluid view in a tab. Once the user switches tabs and goes back to the one with the fluid we should stop and restart the animation as well. In this case the UIApplicationWillResignActiveNotification and UIApplicationDidBecomeActiveNotification won't do the trick and we need to use for instance viewWillAppear/Disappear.

What do you think?

After applications goes to background and returns to foreground BAFluidView causes memory issue and app crashes with error : Terminated due to memory issue . I thinks something strange is happening in getBezierPathValues method but ca't figure it out.

Can you please give some idea how to fix this?

It would be cool if the accelerometer was used to influence how to fluid behaves. I guess that would require some sort of physics simulation, but it would still be cool :)

Hi, I'm trying to implement this great lib on swift, by writing this code:

    let fluidView = BAFluidView(frame: self.view.frame, startElevation: 0.9)!
    
    fluidView.strokeColor = UIColor.green
    fluidView.fillColor = Constants.COLOR_BLUE
    fluidView.keepStationary()
    fluidView.startAnimation()
    
    self.view.addSubview(fluidView)

and here is the preview:

I've been changing the value of startElevation from 0.1 to 9000, but the height of wave didn't change. I want to achieve that the height of wave is 1/4 of the height screen.

Thank you.

If I start the app while holding my phone in my hand in an upright position, the tilting functionality works well. However, if app is launched while the device is flat on a desk or counter top, the tilting functionality will not work once the device is picked up.

1. Fill layer should be calculated on the view's bounds, not its frame. Transformations aren't applied to the frame property when the view is scaled, so the fill level isn't properly adjusted. From Apple:

Views have both a frame (coordinates in superview's coordinate system) and bounds (coordinates in own coordinate system) property, but if you transform a view, you should not use or rely on the frame property anymore. If you are using transformations, work with the bounds property only, not the frame property, as transformations are applied to the bounds, but aren't necessarily reflected accurately in frame.

2. Added kCAMediaTimingFunctionEaseInEaseOut timing function to fillTo()'s CAKeyframeAnimation for a nice, cold, smooth pour.

I added BAFluidView to my screen and I use SWRevealViewController to menu navigation. IF I started to swipe in the menu, the View animation starts to lagging until I release the pull.

Hey, nice view, but in Swift the kBAFluidViewCMMotionUpdate doesn't work. Can you help me?

    private func addFluidIndicator() {
        if self.motionManager.deviceMotionAvailable
        {
            self.motionManager.deviceMotionUpdateInterval = 0.3
            self.motionManager.startDeviceMotionUpdatesToQueue(NSOperationQueue.mainQueue(), withHandler: { (deviceManager, error) -> Void in

                guard let deviceManager = deviceManager else { return }

                let nc = NSNotificationCenter.defaultCenter()
                let userInfo = NSDictionary(object: deviceManager, forKey: "data")
                nc.postNotificationName(kBAFluidViewCMMotionUpdate, object: self, userInfo: userInfo as [NSObject : AnyObject])
            })
        }

        let fluidView           = BAFluidView(frame: UIScreen.mainScreen().bounds, startElevation: 0.5)
        fluidView.fillColor     = UIColor.blueColor()
        fluidView.strokeColor   = UIColor.whiteColor()
        fluidView.keepStationary()
        fluidView.startAnimation()
        fluidView.startTiltAnimation()
        self.view.addSubview(fluidView)
    }

Great API, I think you could add the option for the user easily to change the speed by changing the value 7 on verticalAnimation.duration inside the method fillTo to a variable that the user of the API could set.

On adding a new BAFluidView to the same container view there is an issue where you can not animate it.

Other than that you work is great @antiguab 👍

Improvements you can do:

1. Add a variable to set the Wave Crest speed.
2. Add the Swift 5 version.

To reproduce: Start example app in landscape orientation Swipe down to get to Tilt example Notice incorrect Tilt (see screenshot) Changing orientation of device incorrectly changes fluid level (to near zero)

Note: Tilt does work correctly if you start app in portrait orientation

It seems like the app runs out of memory after a certain period of time.

Here is a console log:

malloc: can't allocate region
*** mach_vm_map(size=939524096) failed (error code=3) AppName
<img width="555" alt="Screenshot 2019-12-19 at 21 38 44" src="https://user-images.githubusercontent.com/3489125/71204297-7ae68800-22a8-11ea-855d-e5af690c9d16.png">
(7620,0x101ecebc0) malloc: *** set a breakpoint in malloc_error_break to debug

I'm working on a project where the background liquid "fill" animation will need to be paused by a user interaction. I'd like to have the waves continue to crest, even when the animation is not filling the view.

Have you considered adding something like this?

I'm struggling with the implementation, but if it's easy, could you share some initial direction?

Thanks!

I am trying to animate the FluidView from top (1.0) to bottom (0.0) On doing so, the FluidView just remains at the top, without any reverse animation.

I tried animating from 1.0 to 0.1, with a fillDuration of 7, but the FluidView just quickly animates to 0.1 in one second.

Here is the code for reference:

fluidView = BAFluidView(frame: fluidViewFrame, maxAmplitude: 25, minAmplitude: 20, amplitudeIncrement: 5, startElevation: 1.0)
fluidView.backgroundColor = LIGHTER_GRAY
fluidView.fillAutoReverse = false
fluidView.fillDuration = 7
fluidView.strokeColor = OFF_WHITE
fluidView.fillRepeatCount = 1
fluidView.fillColor = WHITE
fluidView.fill(to: 0.0)