GestureView | 手势密码

Instead of just not moving the image view at all when its y coordinate is outside of the specified range, you should still allow the image view to be moved downwards if it is too high, and upwards if it is too low.

It would be easier to specify in which situations you don't want the image view to be moved:

• y < 161 and panning upwards
• y > 561 and panning downwards

Also, the reason why you can move it out of the valid y range by dragging very fast is because you only check whether the image view's y coordinate is in the range before moving it, but not after. You should instead clamp the values when adding translation.y.

You add the SurfaceView by code which will place it at the end of the views hierarchy. This means that it will cover all other views below itself.

Placing it at the first place, all views on top of your SurfaceView, can still draw their interface.

By using the addView method overload where you can set the index you're able to place your SurfaceView at the first place.

Therefore change your code from:

Well, I think your code works as implemented.

1. If you set a transform to (-1|1), e.g. you flip the x-axis, then this flipping will be applied to the "original" coordinate system. In other words, you do not apply a transform to the existing transform matrix, (e.g. flip and flip again), but just modify the original matrix (which is the identity matrix). What you might want is:

Below you will find an updated version of your class that should do what you describe.

Most of the updated code is located at the last section (Guides) near the end, but I have updated your UIGestureRecognizer actions a bit as well as your main init method.

Features:

- A vertical guide for centering a view's position horizontally.

- A horizontal guide for centering a view's rotation at 0 degrees.

- Position and rotation snapping to guides with tolerance values (snapToleranceDistance and snapToleranceAngle properties).

- Animated appearance / disappearance of guides (animateGuides and guideAnimationDuration properties).

- Guide views that can be changed per use case (movementGuideView and rotationGuideView properties)

First you will have to convert the textview to imageview.

You can create an Bitmap of any View using buildDrawingCache() and getDrawingCache()

You are moving tabBarController, but as I understand you want to move menuViewController. Try this:

Just wanted to mention how I "solved" this.

Like so many of these types of things, I had to figure out a completely different way to do it, as opposed to trying to shoehorn to the point of hacking.

The way that I dealt with it was to create a transparent UIView that I placed in the view hierarchy over the MapView. I then added my interactive elements to this view, and flushed everything when I was done.

It has a bit of oddness when you click elsewhere, but nothing even close to the damage that was done if the map panned or zoomed. I suspect that I'll be able to work out the oddness with a bit of thought.

You have to use the UIPangesture states so you can find out what states you're in. you can do that using a switch and check for the .changed, .ended, .cancelled states.

Just in case -- have you checked if your controlTopView is not visible simply because it has nothing visible to draw? In your code snippet, the controlTopView only has a transparent background color and a blur effect (which wouldn't do anything to the solid red behind it).