In my situation, I need to change UIView itself in draggingBlocks. And I think add (id self) in draggingBlocks is helpful.

I'm not sure if there is any problem with it, and these code run well in my app. If I'm wrong , please tell me. Thank you

1. I though it would be fun to alter the background color & alpha of view while they moved so I tried out these blocks but the views do not land on the X,Y coords I leave them on. They jump a little. My Code is:

    __weak typeof(timerView) weakSelf = timerView;
    [timerView setDraggingStartedBlock:^
     {
         weakSelf.backgroundColor=switchColor;
         weakSelf.alpha = 0.9f;
     }];
    [timerView setDraggingEndedBlock:^
     {
         weakSelf.backgroundColor=[UIColor whiteColor];;
         weakSelf.alpha = 1.0f;
     }];

Without these blocks the views stop in the correct place. Is there something I can do to resolve this? It's the EndedBlock that's the issue. Even an empty block caused the view to just at the end.

Not mission critical, just nice to try out the code.

@andreamazz I tried to override the variable draggingStartedBlock, draggingEndedBlock with didSet in order to know when the event is fired and call a function afterwards. However, I could not figure out how I can get the notification from draggingEndedBlock and seems it is never called when I test. and the delegate function is never called as well.

would be much appreciated if you could provide examples on how to use these variables

Here is my code:

 override var draggingEndedBlock: ((UIView?) -> Void)!{
        didSet{
            print("drag ended")
            delegate?.updatePosition(self.frame, messageId: (self.message?.id)!)
        }
    }

Anyone could help?

For example, UIImagePickerController is sometimes grayed-out or unresponsive, and UIActivityViewController, when presented, has its frame off the screen. I'll have to look for more details, but I know the issue is not present in my (older) fork: https://github.com/rsmoz/UIView-draggable

When i stop drag a button, the button's action will called, i tryed this: [self.roundButtonShadowView setDraggingStartedBlock:^(UIView *view) { @strongify(self) self.roundButton.userInteractionEnabled = NO; }]; [self.roundButtonShadowView setDraggingEndedBlock:^(UIView *view) { @strongify(self) self.roundButton.userInteractionEnabled = YES; }]; but now worked, the button's action is still be called... Sorry for my bad English.

if (sender.state == UIGestureRecognizerStateEnded && self.draggingEndedBlock) { self.layer.anchorPoint = CGPointMake(0.5, 0.5); self.draggingEndedBlock(self); }

Just wondering why one would need to have the drag end block implemented to have the anchor point reset.

Hi, could the object move/drag outside of its parent ?

let's say uibutton added as subview in uiscrollview and I want to make the uibutton draggable in whole self.view not only inside uiscrollview

any hint?

    if (newXOrigin <= cagingAreaOriginX ||
        newXOrigin + CGRectGetWidth(self.frame) >= cagingAreaRightSide ) {
        newXOrigin = CGRectGetMinX(self.frame);

    }
    if(newYOrigin <= cagingAreaOriginY ||
       newYOrigin + CGRectGetHeight(self.frame) >= cagingAreaBottomSide)
    {
                    newYOrigin = CGRectGetMinY(self.frame);
    } 

I was having problems with small draggable views and quick pan velocities where the gesture events would end up outside of the handle rect if the gesture was quick enough. Is there a specific reason this was being checked on all event states?

EDIT: Also apparently some Atom generated whitespace fixes?

Hi @andreamazz,

I've added tests and integrated coveralls.io for your project during the CocoaPods TestJam. Please note that you will need to enable coveralls.io for the repo using your GitHub account, I don't have admin rights to do that. Check this post if you need more info on coveralls.

We're 100% covered :)

This pull request adds the functionality a caging area for the draggable view, in which the view can not be dragged out of.

To add a caging area, set the cagingArea property on the view:

[view enableDragging];
CGRect cagingArea = <some CGRect>;
view.cagingArea = theCagingArea;

and to disable the caging functionality, set the cagingArea to CGRectZero:

view.cagingArea = CGRectZero;

This also adds a UISwitch to the demo project to showcase this behavior. In this demo, the caging area is the frame of the FPViewController's view.

@import directive is causing a compiler issue "Use of '@import' when C++ modules are disabled, consider using fmodules and fcxx-modules" when included in .mm files.

If cagingArea is set and you swipe the view quickly it will go out of bounds, for example I turned off allowing the view to move along the Y axis, but it does if I swipe it down or up fast enough.

Commenting out function "adjustAnchorPointForGestureRecognizer" seems to fix my issue, but still testing...

Hi,

I want to move the subviews of a view. Actually if I set enableDragging in a subview it doesn't move, but if I set into the superview it moves. Is there I have to config into the superview to enable pan gesture into subviews?

Thanks for your work!

In Demo, FPViewController.m , I use draggingStartedBlock

- (IBAction)actionSwitch:(UISwitch*)sender {
    [self.draggableViews enumerateObjectsUsingBlock:^(UIView* obj, NSUInteger idx, BOOL *stop) {
        [obj setDraggable:sender.isOn];
        obj.draggingStartedBlock= ^(){
            NSLog(@"dragging!~!~!~!");
        };
    }];
}

when I drag UIView slowly, it works well, but when I drag UIView fast enough, draggingStartedBlock doesn't work.

I think the problem is , when - (void)handlePan:(UIPanGestureRecognizer*)sender is called, sender.state is alreay 'UIGestureRecognizerStateChanged' . I'm not sure and I wonder whether there are some good solutions.

THANK YOU.