fhadillam / android-multitouch-controller

Automatically exported from code.google.com/p/android-multitouch-controller
0 stars 0 forks source link

Reuse position and scale information #18

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
onResume();

The images to be in the same position. Instead they move to a new position. 

The latest version. Windows 8. 

My app does not need to rotate the screen orientation. It is always portrait. I 
am using your PhotoSortrView class and modifying it for my app.  Can I locate 
and disable your rotation method so that within PhotoSortrView.load(), it will 
successfully keep the images in the same position? Thanks. 

Original issue reported on code.google.com by benni.fa...@gmail.com on 12 Jan 2014 at 11:48

GoogleCodeExporter commented 9 years ago
Edit: if (this.maxX < SCREEN_MARGIN)
                    cx = SCREEN_MARGIN;
                else if (this.minX > displayWidth - SCREEN_MARGIN)
                    cx = displayWidth - SCREEN_MARGIN;
                if (this.maxY > SCREEN_MARGIN)
                    cy = SCREEN_MARGIN;
                else if (this.minY > displayHeight - SCREEN_MARGIN)
                    cy = displayHeight - SCREEN_MARGIN;

Was firing too often and that is why they moved. It fired when the images were 
on the screen. 

Original comment by benni.fa...@gmail.com on 13 Jan 2014 at 3:44

GoogleCodeExporter commented 9 years ago
I don't understand, did you solve the problem or is there still an issue? 

You can disable screen rotation with a simple attribute setting in 
AndroidManifest.xml if I remember right...

Original comment by luke.hutch on 15 Jan 2014 at 10:50

GoogleCodeExporter commented 9 years ago
It's solved thanks. Well I hacked it. I just commented out those lines for now, 
which seems to make it behave nicely. When they were not commented out, the 
images could not retain position, scale, or angle. If that isn't the case for 
others, maybe I just changed something in my code. Thank you, Awesome project :)

Original comment by benni.fa...@gmail.com on 15 Jan 2014 at 11:46

GoogleCodeExporter commented 9 years ago
On second thought I was probably meant to set maxX and maxY. That could have 
been my issue, I didn't define them. If they fired too much they must have been 
too small.   

Original comment by benni.fa...@gmail.com on 15 Jan 2014 at 12:04

GoogleCodeExporter commented 9 years ago
OK, glad you solved it!

Original comment by luke.hutch on 16 Jan 2014 at 5:37