- Mar 08, 2016
-
-
- Mar 09, 2014
-
-
- Nov 21, 2013
-
-
Emmanuele Bassi authored
-
- Nov 20, 2013
-
-
Emmanuele Bassi authored
-
Emmanuele Bassi authored
It's a pretty pointless test, which got dropped in newer releases of Clutter.
-
Emmanuele Bassi authored
If we allow content repeats on the texture nodes, then we need to use the "automatic" wrap mode for the texture layer in the pipeline, instead of the clamp-to-edge one. Reported-by: Matthew Watson <matthew@endlessm.com> Signed-off-by: Emmanuele Bassi <ebassi@gnome.org> (cherry picked from commit 5b614cda ) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
-
When allocating or asking for preferred width/height on a ClutterText, it can notify a change on buffer/text/max-length if no text has been set. https://bugzilla.gnome.org/show_bug.cgi?id=703882 (cherry picked from commit eed94960 ) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
-
Emmanuele Bassi authored
The implicitly created transitions are removed when complete by the implicit transition machinery. The remove-on-complete hint is for user-provided transitions. https://bugzilla.gnome.org/show_bug.cgi?id=705739 (cherry picked from commit b50e1c3b ) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
-
Emmanuele Bassi authored
ClutterTransition:remove-on-complete uses the ClutterTimeline::stopped signal, as it's the signal that tells us that the timeline's duration has fully elapsed. (cherry picked from commit edf00747 ) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
-
In clutter_allocate_align_fill(), x2/y2 may be set twice for no particular reason; save a couple of lines by not doing this. https://bugzilla.gnome.org/show_bug.cgi?id=703809 (cherry picked from commit 5bab9a86 ) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
-
Currently, BoxLayout interprets the box passed into allocate() in a fairly peculiar way: - in the direction of the box, all space between [xy]1 and [xy]2 is distributed among children (e.g. children occupy the entire width/height of the box, offset by [xy]1) - in the opposite direction, expanded children receive space between [xy]1 and the height/width of the box (e.g. children occupy the width/height of the box minus [xy]1, offset by [xy]1) The second behavior doesn't make much sense, so adjust it to interpret the box parameter in the same way as the first one. https://bugzilla.gnome.org/show_bug.cgi?id=703809 (cherry picked from commit 5dd2dcf1 ) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
-
Just as BoxLayout, BinLayout uses an odd interpretation of the box passed into allocate(): to define a child area of (w x h) starting at (x, y), callers need to pass a box of (x, 2 * x + w, y, 2 * y + h). This behavior is just confusing, change it to use the full box for child allocations. https://bugzilla.gnome.org/show_bug.cgi?id=703809 (cherry picked from commit 40a1903d ) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
-
Whether a child should receive extra space should be determined by the expand property, not [xy]_fill (which just determine how additional space should be used). The behavior is already correct when using the ClutterActor:[xy]_expand properties, but needs fixing for the corresponding ClutterBoxLayoutChild property. https://bugzilla.gnome.org/show_bug.cgi?id=703809 (cherry picked from commit 8e850ff3 ) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
-
Currently the default values according to their param spec don't match the actually used defaults, so update the former to reflect the actual behavior. https://bugzilla.gnome.org/show_bug.cgi?id=703809 (cherry picked from commit c14bd84e ) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
-
https://bugzilla.gnome.org/show_bug.cgi?id=706450 (cherry picked from commit 05f56aff ) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
-
The child size is a float, not an int. https://bugzilla.gnome.org/show_bug.cgi?id=707808 (cherry picked from commit ac70bd35 ) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
-
https://bugzilla.gnome.org/show_bug.cgi?id=707774 (cherry picked from commit 5c035f21 ) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
-
Currently this is only the case when the actor's x-expand/x-align flags have been set and clutter_text_compute_layout_offsets() is used. https://bugzilla.gnome.org/show_bug.cgi?id=705779 (cherry picked from commit 986e46dc ) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
-
Emmanuele Bassi authored
The range of a device could be 0, so we need to bail out from the scaling during the axis translation. https://bugzilla.gnome.org/show_bug.cgi?id=707033 (cherry picked from commit fb8eacfb ) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
-
https://bugzilla.gnome.org/show_bug.cgi?id=708850 (cherry picked from commit 067fcc36 ) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
-
This is what we already do in the actual size requests, it makes sense to do the same in the space calculations. https://bugzilla.gnome.org/show_bug.cgi?id=709434 (cherry picked from commit 3435d017 ) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
-
The calculation (n - 1) * spacing to compute the total spacing is only correct for n >= 1 - if there are no visible rows/cols, the required spacing is 0 rather than negative. https://bugzilla.gnome.org/show_bug.cgi?id=709434 (cherry picked from commit 44b1a808 ) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
-
https://bugzilla.gnome.org/show_bug.cgi?id=709762 (cherry picked from commit ccd2d4c0 ) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
-
- Oct 10, 2013
-
-
Emmanuele Bassi authored
ClutterTextureNode will do that for us when converting the ClutterColor to a CoglColor, so we can simply pass a white color with the correct alpha channel.
-
- Sep 27, 2013
-
-
Bastien Nocera authored
It's a flags property, not an enum one. https://bugzilla.gnome.org/show_bug.cgi?id=708922
-
- Sep 25, 2013
- Aug 27, 2013
-
-
- Jun 27, 2013
-
-
Emmanuele Bassi authored
The Wayland backend is based on Cogl, so we need to turn on the SUPPORT_COGL flag to avoid breaking the build; this always went unnoticed because we usually build the Wayland client backend with the X11 backend. Reported-by: Ross Burton <ross.burton@intel.com> (cherry picked from commit 1fb0295b ) Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
-
- Jun 25, 2013
-
-
Adel Gadllah authored
Cogl now lazy loads the textures so we cannot rely on getting NULL from cogl_texture_new_with_size so we have to allocate it by ourselves. https://bugzilla.redhat.com/show_bug.cgi?id=975171
-
- Jun 18, 2013
-
-
Cosimo Cecchi authored
When the cursor visibility changes, we have to relayout the ClutterText actor instead of just redrawing it - as the cursor changes the PangoLayout size, a size request cycle is needed. https://bugzilla.gnome.org/show_bug.cgi?id=702610
-
- Jun 12, 2013
-
-
Lionel Landwerlin authored
When setting the font using clutter_text_set_font_description(), the font settings on a ClutterText actor can be reset when there is a dpi changes signaled by the backend. https://bugzilla.gnome.org/show_bug.cgi?id=702016
-
1ddef957 had its logic the wrong way round, a gesture should begin as soon as the requested number of touchpoints is reached. Correcting this fixes tap events https://bugzilla.gnome.org/show_bug.cgi?id=700980
-
Fix a function call to set the cull-face mode of the back_pipeline: the function was called on the 'front-pipeline' instead of the back-pipeline.
-
Emmanuele Bassi authored
Especially on actors that are not parented and get destroyed.
-
Emmanuele Bassi authored
-
Emmanuele Bassi authored
When we changed the MetaGroup to handle internal effects, we updated has_effects(), but forgot to fix the equivalent has_constrains() and has_actions() method. Now, if we clear the constraints or the actions on an actor, and we call has_constraints() or has_actions(), we get an false positive.
-
- Jun 11, 2013
-
-
Matthias Clasen authored
Devices can disappear at any time, causing XIQueryDevice to throw an error. At the same time, plug a memory leak. https://bugzilla.gnome.org/show_bug.cgi?id=701974
-