Jump to content

Search the Community

Showing results for tags 'transformation'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • GreenSock Forums
    • GSAP
    • Banner Animation
    • Jobs & Freelance
  • Flash / ActionScript Archive
    • GSAP (Flash)
    • Loading (Flash)
    • TransformManager (Flash)

Product Groups

  • Club GreenSock
  • TransformManager
  • Supercharge


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Personal Website



Company Website



Found 2 results

  1. Hi, Loving the library so far guys just have a quick question. Is there a simple way to specify an animations midpoint and set css properties so it applies them via that midpoint? I.E a TweenMax function such as: TweenMax.from > Midpoint > To I realise this is basically how Tweens work and you should aim to chain multiple tweens together in a timeline to create multiple part animations, However I was just curious to see if there was something akin to this i'm missing as couldn't find anything in the documentation? The aim is to make the dots fade to a low opacity at the midpoint (as they rotate behind) then return to full opacity as they return to the front (and end point of the animation) ! Thanks in advance, Oli
  2. Hi all, Another very specific problem just looking for ideas, after being stuck on it for over a week. I am using the TransformationAroundCenter plugin for all of my transformations, namely rotation and scaling. I also know that you can rotate and scale at the same time, as long as you issue them all in the same command. However, i would like to know if there's a way to do these transformations separately? For example, rotate an object with duration of 10 seconds, and after 1 second after the rotation starts, start scaling. Right now, this doesn't seem to be possible. I looked into the source code of TransformationAroundCenter and TransformationAroundPoint plugins, it seems they operate on transformation matrices, which would explain why those separate transformations would conflict with each other. Could there be any way around this (for example, implement a transformationAroundCenter plugin myself that does not involve transformation matrices?), or is this problem inherently insolvable? Thank you