1. 20 Jul, 2016 1 commit
  2. 12 Apr, 2016 1 commit
  3. 03 Jan, 2015 1 commit
    • Emmanuele Bassi's avatar
      WARNING: Massive revert commit · 77ec8774
      Emmanuele Bassi authored
      Revert all the work that happened on the master branch.
      
      Sadly, this is the only way to merge the current development branch back
      into master.
      
      It is now abundantly clear that I merged the 1.99 branch far too soon,
      and that Clutter 2.0 won't happen any time soon, if at all.
      
      Since having the development happen on a separate branch throws a lot of
      people into confusion, let's undo the clutter-1.99 → master merge, and
      move back the development of Clutter to the master branch.
      
      In order to do so, we need to do some surgery to the Git repository.
      
      First, we do a massive revert in a single commit of all that happened
      since the switch to 1.99 and the API version bump done with the
      89a2862b commit. The history is too long
      to be reverted commit by commit without being extremely messy.
      77ec8774
  4. 03 Jul, 2013 1 commit
  5. 05 Apr, 2013 1 commit
  6. 18 Jun, 2012 1 commit
  7. 08 Jun, 2012 2 commits
    • Emmanuele Bassi's avatar
      property-transition: Verify the interval on compute_value() · b21cb294
      Emmanuele Bassi authored
      By checking if the interval is valid inside compute_value() we can catch
      the cases where the interval values of a PropertyTransition are set
      after the transition has been added to an Animatable instance - i.e. the
      following code:
      
        let transition = new Clutter.PropertyTransition();
        transition.set_property_name('opacity');
        actor.add_transition('opacityAnim', transition);
        transition.set_to_value(0);
      
      should be equivalent to:
      
        let transition = new Clutter.PropertyTransition();
        transition.set_property_name('opacity');
        transition.set_to_value(0);
        actor.add_transition('opacityAnim', transition);
      
      instead of emitting a warning.
      b21cb294
    • Emmanuele Bassi's avatar
      transition: Use current values if no interval is defined · 7660f5d0
      Emmanuele Bassi authored
      Once a ClutterPropertyTransition is attached to a ClutterAnimatable, if
      no interval is set we can simply use the current state of the property
      to define the from and to values. This allows the creation of property
      transitions from the current state of the Animatable instance without
      excessive verbosity.
      7660f5d0
  8. 20 Mar, 2012 1 commit
  9. 15 Mar, 2012 1 commit