1. 06 Jan, 2019 1 commit
  2. 06 Dec, 2018 1 commit
  3. 05 Dec, 2018 1 commit
  4. 18 Nov, 2018 2 commits
  5. 09 Nov, 2018 1 commit
  6. 06 Nov, 2018 2 commits
  7. 25 Jan, 2018 1 commit
    • Ray Strode's avatar
      clutter/stage: Set framebuffer state directly · 58bb61e1
      Ray Strode authored
      clutter_set_viewport always operates on the draw fb, but
      mutter sometimes has an offscreen fb it uses instead.
      This commit uses the non-deprecated, clutter_framebuffer_set_viewport
      function, which takes an explicit fb argument.
      Closes: !2
  8. 20 Dec, 2017 1 commit
  9. 20 Sep, 2017 1 commit
    • Jonas Ådahl's avatar
      clutter: Fix capture_into on non-origin view · ba194bd1
      Jonas Ådahl authored
      The capture_into() function wrote out of bounds when capturing from a
      non-origin view (not positioned at (0,0)). At the time of
      implementation, this API was used to capture pixels across views into a
      single data buffer, but the way it's used, and the way views may work
      now, makes this impossible to do properly.
      So remove the ability to capture into a pre-allocated buffer from
      multiple views, and complain if the passed rectantgle overlapps with
      multiple views. This removes the broken offset calculation all
      together, fixing the bug motivating this change.
  10. 29 Aug, 2017 1 commit
  11. 14 Jul, 2017 3 commits
  12. 03 Jul, 2017 1 commit
  13. 23 May, 2017 1 commit
  14. 09 May, 2017 1 commit
  15. 07 Apr, 2017 2 commits
  16. 17 Oct, 2016 1 commit
  17. 19 Sep, 2016 1 commit
  18. 15 Sep, 2016 2 commits
  19. 09 Sep, 2016 1 commit
    • Jonas Ådahl's avatar
      clutter: Compress instead of discard motion events · d893adb2
      Jonas Ådahl authored
      Clutter discards any motion event if next event happens to also be a
      motion event. This is problematic when the motion event carries
      relative motion deltas, since the information about them is completely
      Until we have moved away made the stage stop discarding motion events,
      lets work around the issue by compressing them, effectively adding
      multiple relative motion deltas together, would one be discarded.
  20. 06 Sep, 2016 1 commit
  21. 20 Jul, 2016 6 commits
    • Jonas Ådahl's avatar
      clutter: Add capture API for reading stage pixels · ff6186f1
      Jonas Ådahl authored
      clutter_stage_capture should be used instead of directly utilizing
      cogl's read_pixels API's.
    • Jonas Ådahl's avatar
      Use signals instead of onscreen framebuffer frame callbacks · 28a898a2
      Jonas Ådahl authored
      CoglFrameInfo is a frame info container associated with a single
      onscreen framebuffer. The clutter stage will eventually support drawing
      a stage frame with multiple onscreen framebuffers, thus needs its own
      frame info container.
      This patch introduces a new stage signal 'presented' and a accompaning
      ClutterFrameInfo and adapts the stage windows and past onscreen frame
      callbacks users to use the signal and new info container.
    • Jonas Ådahl's avatar
      Introduce regional stage rendering · 566c28bd
      Jonas Ådahl authored
      Add support for drawing a stage using multiple framebuffers each making
      up one part of the stage. This works by the stage backend
      (ClutterStageWindow) providing a list of views which will be for
      splitting up the stage in different regions.
      A view layout, for now, is a set of rectangles. The stage window (i.e.
      stage "backend" will use this information when drawing a frame, using
      one framebuffer for each view. The scene graph is adapted to explictly
      take a view when painting the stage. It will use this view, its
      assigned framebuffer and layout to offset and clip the drawing
      This effectively removes any notion of "stage framebuffer", since each
      stage now may consist of multiple framebuffers. Therefore, API
      involving this has been deprecated and made no-ops; namely
      clutter_stage_ensure_context(). Callers are now assumed to either
      always use a framebuffer reference explicitly, or push/pop the
      framebuffer of a given view where the code has not yet changed to use
      the explicit-buffer-using cogl API.
      Currently only the nested X11 backend supports this mode fully, and the
      per view framebuffers are all offscreen. Upon frame completion, it'll
      blit each view's framebuffer onto the onscreen framebuffer before
      Other backends (X11 CM and native/KMS) are adapted to manage a
      full-stage view. The X11 CM backend will continue to use this method,
      while the native/KMS backend will be adopted to use multiple view
    • Jonas Ådahl's avatar
      compositor: Don't access use the onscreen framebuffer directly · 7f0e6b9b
      Jonas Ådahl authored
      Instead of assuming there is a single onscreen framebuffer, use the
      helper functions for setting the frame callback and getting the frame
    • Jonas Ådahl's avatar
      ClutterStageCogl: Let the sub-classes handle the onscreen · 767e1212
      Jonas Ådahl authored
      In preperation for having allowing drawing onto multiple onscreen
      framebuffers, move the onscreen framebuffer handling to the
      corresponding winsys dependent backends.
      Currently the onscreen framebuffer is still accessed, but, as can seen
      by the usage of "legacy" in the accessor name, it should be considered
      the legacy method. Eventually only the X11 Compositing Manager backend
      will make use of the legacy single onscreen framebuffer API.
    • Jonas Ådahl's avatar
      Don't use config.h in clutter and cogl · bf71cb2e
      Jonas Ådahl authored
      In cogl use cogl-config.h and in clutter use clutter-build-config.h. We
      can't use clutter-config.h in clutter because its already used and
  22. 03 May, 2016 1 commit
  23. 12 Apr, 2016 1 commit
  24. 01 May, 2015 1 commit
  25. 03 Mar, 2015 2 commits
    • Emmanuele Bassi's avatar
      Drop the UProf dependency · 25329280
      Emmanuele Bassi authored
      Nobody has been compiling Clutter with profiling enabled in a long time.
      UProf itself hasn't been updated in 5 years, and it still depends on
      deprecated components like dbus-glib, with no port to GDBus in sight.
      The profiling code was moderately useful in the past, but these days
      it's probably better to profile Cogl than Clutter itself; timing
      information can be extracted by the timestamp on each diagnostic message
      that is now available by default in the CLUTTER_NOTE macro, and we can
      add ad hoc counters where needed.
    • Emmanuele Bassi's avatar
  26. 16 Feb, 2015 1 commit
    • Lionel Landwerlin's avatar
      stage: Process state update event immediately · a9f2300a
      Lionel Landwerlin authored
      The _clutter_stage_update_state() function is currently putting events
      into the Clutter event queue. This leads to problems in the gdk
      backend because there are assumptions upon the numbers of queued
      events, and how many of them should be moved from the main event queue
      to the ClutterStages' event queues.
      This change triggers the processing of the state update events on the
      stage directly, so the main event queue retains the expected number of
  27. 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.
  28. 01 Jan, 2015 1 commit
    • Emmanuele Bassi's avatar
      Remove global "actor id" · 1b9650da
      Emmanuele Bassi authored
      It's absolutely, positively pointless. Every surviving call has long
      since been deprecated, and should have not been public in the first