Jump to content


  • Posts

  • Joined

  • Last visited

x0b's Achievements



  1. I've done a factory reset from the settings which has wiped all data, the superuser app remains on there but all others are gone. The stock browser still exhibits the problem. I am happy to remove root access and restore the phone to another firmware, I will try and find out how to do this tomorrow and then report back once done.
  2. Hi, It's fine on Chrome and Firefox latest versions, sorry I forgot to mention that!
  3. Something called superuser, I did it a long time ago and don't really know anything about Android so I can't be more helpful than that I'm afraid!
  4. Hi Jonathan, It's Android 4.1.2, it's been rooted so I could upgrade to this firmware. http://www.greensock.com/draggable/ If you could test the above throw demo on your S2 and see if it's ok in the stock browser that would be appreciated. Thanks
  5. Hi, I'm testing out the draggable demos from this site on a Samsung Galaxy S2 GT-I9100 Android version 4.1.2 in the stock browser and I cannot actually drag anything, the draggable item moves to the correct place upon drag ending but does not move around whilst being dragged. Are you aware of this problem and do you know if it's fixable? Cheers
  6. Hi, I'm using scrollTop on a div and would like the native scroll bar to show on mobile. It does on the desktop and Chrome on Android 4.1.2 but doesn't on iOS 7.1.1 on iPhone 4S in either Safari or Chrome. I have set -webkit-overflow-scrolling:touch in the css but it's not helping. Any ideas? Thanks
  7. Hi, I've managed to get it working exactly as required. http://codepen.io/x0b/pen/qmGis When not dragging I set the draggables to dragResistance 1 so they can't be dragged. Then as soon as a touch is registered I start to record the direction the drag is going whilst touchmove fires and then change the dragResistance of the desired draggable to suit, then reset all dragResistance settings back to 1 when the touchend event fires. I could probably optimise this more by just using draggables built in drag events but I'm very happy with how it works and I don't get any stuttering like I did when using enable() and disable(). Cheers!
  8. Hi, Further to this discussion, I'm having some issues with the performance of disabling draggable instances, the site I am making will be for smart phones and I am seeing slowdown and performance problems when testing on iPhone 4S iOS 7.1.1 (it's worse with other less powerful phones). My setup is similar to Webls, I have a main container that has draggable scrollTop on it and inside that I have many elements with draggable x set on them. Here is a codepen to demonstrate : http://codepen.io/x0b/pen/gbBcu You'll notice that when dragging vertically you can also drag the horizontal draggables and vice-versa. Although it works pretty smoothly, this is unwanted behaviour as I want to either drag vertically or drag one of the horizontal draggables on it's own. The following app exhibits the exact behaviour I want to recreate, I think it works very smoothly and is a great UX, to be able to recreate it with Greensockk would be amazing! https://itunes.apple.com/gb/app/bbc-news/id377382255?mt=8 So, this code pen demonstrates the desired relationship between vertical and horizontal: http://codepen.io/x0b/pen/pcgEm The problem now is performance, when i flick one of the horizontal rows I get a stutter where it is disabling the vertical drag. It's also very hard to do a horizontal drag every time because the threshold between a horizontal gesture and vertical gesture is so close. This is also apparent when trying to drag vertically when touching on one of the rows. I wonder if you have any ideas about how I can overcome this performance problem? It seems disabling and/or enabling a draggable instance uses up enough juice to causes jerky animations. I'm not sure what goes on under the hood but maybe there is a way to do a lighter version of disable/enable that won't cause glitches? Even if there was a way of adjusting the '3px' click threshold to be a higher value, that might help? I've also tried setting the dragResistance to 1 in the hope it would disable in a 'light' way but that didn't work out well, although that approach seems like it could be good...
  9. Hi, Yeah I too am not a fan of custom ones. I'll do some more testing and see whether the slight performance trade off warrants one or not. Thanks a lot for everyones help
  10. Hi, Thanks for the replies. I'd like the performance of a Y transform compared to scrollTop but I also definitely want the scroll bar to show the user where they are on the page. What would you suggest is the best way of accomplishing this? A custom scroll bar? Thanks
  11. Hi Rodrigo, Thanks for the answer, you're right - it makes sense to use a wrapper div instead of the body. Is there a way to show a native scroll bar when dragging? Thanks Edit : I realised using scrollTop instead of y means a scroll bar is shown, this also seems to make the animation quite jerky - is there something I need to change here or is scrollTop animation not as smooth as y animation?
  12. I'm a bit stuck due to the limitations of not getting a scroll event fire when scrolling the body on touch devices, can Draggable overcome this? I was thinking it may be possible to use Draggable on the body element and turn off native scrolling, therefore simulating natural scrolling and also enabling any desired updates whilst Draggable is doing its thing... Am I barking up the wrong tree?
  13. Hi Carl, Thanks, I tried the above syntax but it didn't work. I now realise from your Codepen that appending [0] to the draggable instance var is what I needed to do to access the vars. Thanks a lot
  14. Is it possible to update the snap array on a draggable instance to something else after creation? Say I have the snap values set to an array, but then later some values in that array change, can I change the old snap array to the new array, therefore updating the snap values? Thanks
  15. Hi Carl, Thanks so much, the last solution is working perfectly As advised I added in a bit to record the progress prior to reinitialising the tween and then setting it immediately afterwards so the element tween was in the same place, and now it works exactly as I needed. I did have a quick fiddle with percentage based positioning, would this eradicate the need to reinitialise the tween or would I still need to follow that process? This element is the only one in the site that reacts to the browser size, everything else is contained in a fixed width div so I haven't needed to use percentages previously. Once again thanks so much!