| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
It's a pretty pointless test, which got dropped in newer releases of
Clutter.
|
|
|
|
|
|
|
|
|
|
|
| |
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 5b614cda1cd6032d7a0b1d9823219bc336086246)
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 eed94960562693e489354afb2a78a355301515fa)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
|
|
|
|
|
|
|
|
|
|
| |
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 b50e1c3b628c0238da0d1ea89853b53ef06fa2ef)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
|
|
|
|
|
|
|
|
|
| |
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 edf00747ef3bb955ad48a2191cdec33524156298)
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 5bab9a8655346290f7ee0e4af972e3d085a6b818)
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 5dd2dcf14ff4676ac4d84ef567d1bca1faaaab7a)
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 40a1903db6dd80445275b3f73a53fd7b7df47017)
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 8e850ff3e4f02d37ec7ecc272eea540ffd29dbcf)
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 c14bd84eefd53c9df891e4d031455fbf75dbb4c3)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
|
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=706450
(cherry picked from commit 05f56affe19468e1e54281230cd23333f94cfebb)
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 ac70bd3503ee7adc9bf6938353e25e81e852bfaf)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
|
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=707774
(cherry picked from commit 5c035f2107cda24a074246d6b083296da2526c07)
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 986e46dc6677a708cd3db8abaf28f09cd2007c4b)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
|
|
|
|
|
|
|
|
|
| |
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 fb8eacfb0256a211ca79366945c8f4eb4962be4e)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
|
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=708850
(cherry picked from commit 067fcc3690b0a354bf0a7b0692aab47fb68a0817)
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 3435d017e27755353123ca8f65bfe3c051102b48)
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 44b1a808c8a74fd3b97367f4819fabcc46a1eb23)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
|
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=709762
(cherry picked from commit ccd2d4c0a7a789e3aea410f9fafd494949fb0c87)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
It's a flags property, not an enum one.
https://bugzilla.gnome.org/show_bug.cgi?id=708922
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 1fb0295ba162507fb798b2b7030f0f45ff252f27)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
1ddef9576d87c98fafbcefe3108f04866630c2cd 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.
|
|
|
|
| |
Especially on actors that are not parented and get destroyed.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=696813
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=696813
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
We want to avoid the pointer getting stale, and causing crashes.
https://bugzilla.gnome.org/show_bug.cgi?id=692706
(cherry picked from commit 19391a9626b087bd4df452e8699d53caa54c350f)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
|
|
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=699675
(cherry picked from commit d1041e1f4f5bedc6331e65a7faf60289f26f7fb0)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When using a ClutterOffscreenEffect, the size of the offscreen buffer
allocated to perform the effect is currently computed using the paint
volume of the actor it's attached to and in the case the paint volume
cannot be computed, the effect falls back to using the stage's size.
If you scale an actor enough so its paint volume is much bigger that
the size of the stage, you can end up running out of memory (which
leads to your application crashing).
https://bugzilla.gnome.org/show_bug.cgi?id=699675
(cherry picked from commit 9c6f3793e832e03ec72c63cd11f28601bf760f5b)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The ClutterActor::paint signal is deprecated, and connecting to it even
to get notifications will disable clipped redraws because of violations
of the paint volume.
The only actual valid use case for notifications of a successful frame
is on the ClutterStage, so we should add new (experimental) API for it,
so that users can actually subscribe to it — at least if you're writing
a compositor.
Shoving a signal in a performance critical path is not an option, and
I'm not sure I want to commit to an API like this yet. I reserve the
right to revisit this decision in the future.
This is a backport of the same commit from the clutter-1.16 branch, and
it introduces new API in a stable series.
https://bugzilla.gnome.org/show_bug.cgi?id=698783
(cherry picked from commit d061a47573fbfec69ed6f2fd02f233e218830a6d)
Signed-off-by: Emmanuele Bassi <ebassi@gnome.org>
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=698674
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=698671
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=698669
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=698668
|