Jump to content

Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Newbie

About cbert

  • Rank
  1. I think I found the issue. My implementation triggered Draggable.create multiple times which lead to this behaviour (basically click event was fired multiple times due to this). But thanks for the quick response!
  2. Are you using 3.6.1 here or still 3.6?
  3. Thanks for the quick response, that is truly amazing speed :-). I tried to replace your file with the /node_modules/gsap/dist/Draggable.min.js and also then tried to replace the non-minified version. Not sure if that's the way to do it, though? Both lead to the same behaviour as before (meaning click event was fired). I also tried to switch to x, y and as far as I can tell I had the same issue. Please let me know if I can help with other testing scenarios!
  4. Hi there, I'm using Draggable with inertia true. The onClick event gets triggered every second time I drag an element (more than 3 pixels), which I thought it should not. With inertia false, it works as expected -> onClick only gets fired if element has not moved more than 3 pixels. Do you see if I do anything wrong here? The example here can't load inertia plugin, but you see my code: https://svelte.dev/repl/c20bf7a911064883a0726c0946d92662?version=3.35.0 Thanks in advance and best regards, Christian PS: Does anyone know
  5. Hi @ZachSaucier Thanks for the quick reply, and more than welcome! Yes, I totally understand that. I will read more into MotionPathPlugin first and if still needed will try to come up with a minimal demo.
  6. Hi there, I'm brand new to gsap, so far I must say, great quality and documentation! Nevertheless, I'm currently stuck with the following issue: I have a pannable and zoomable container (=> transformed container) inside which I move elements around via gsap draggable. To add new elements I'd like to point the pointer to an area inside this container and then add the element in that place. So far, I couldn't find a way to get similar properties as I get with pointerX or pointerY that are relative to the transformed container. Is there any w