To be able to see how it looks like easily.

The prefix widgets appear before any element in the row.

Fixes #297

Fixes #299

This will help us properly maintain the symbols file.

Stop using g_object_get_data() for this, and make the API clearer by
actually requiring HdySwipeable implementation to have a swipe tracker.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

Don't check if the swipeable already has a swipe tracker. This check will
become redundant in the next commit with hdy_swipeable_get_swipe_tracker(),
as a swipeable must always have a swipe tracker now, and causes problems
for HdyStackableBox, as we create the swipe tracker during the mixin
creation, and so can't route hdy_swipeable_get_swipe_tracker() through the
mixin yet.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

Alexander Mikhaylenko authored Jun 28, 2020 and Adrien Plazas committed Jun 30, 2020

And now the interface is a little more similar for C and bindings.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

Alexander Mikhaylenko authored Jun 28, 2020 and Adrien Plazas committed Jun 30, 2020

Make it mandatory.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

Alexander Mikhaylenko authored Jun 28, 2020 and Adrien Plazas committed Jun 30, 2020

Now that get_snap_points() is implemented everywhere, we can easily
reimplement get_range() using it.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

Alexander Mikhaylenko authored Jun 28, 2020 and Adrien Plazas committed Jun 30, 2020

Currently get_range() is mandatory, get_snap_points() is optional. However,
bindings don't have optional methods, and so essentially both are required,
which is redundant in many cases. Instead, let's make get_snap_points()
mandatory and remove get_range(). But first, we need to actually implement
it everywhere.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

I forgot about these, should have tested not only with HdyDeck which will
no-op in those handlers if begin-swipe didn't happen.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

This will help with #167



Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

This will help with #167



Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

The name and the since version are also wrong.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

It was a GtkWidget long time ago. It's not anymore.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

Add (transfer none) to the return value.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

This function will be public, it needs docs.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

The parameter name was wrong.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

Now begin_swipe(), update_swipe() and end_swipe() can be removed.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

Connect to HdySwipeTracker signals instead of implementing interface
functions.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

Connect to HdySwipeTracker signals instead of implementing interface
functions.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

Now that everything is in place, we can do the switch.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

This will replace HdySwipeable's signal and at the same time allow
swipeables to connect to it instead of overriding end_swipe() there,
making it clear the 2 classes are closely related and are only meant to be
used together.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

This will replace HdySwipeable's signal and at the same time allow
swipeables to connect to it instead of overriding update_swipe() there,
making it clear the 2 classes are closely related and are only meant to be
used together.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

This will replace HdySwipeable's signal and at the same time allow
swipeables to connect to it instead of overriding begin_swipe() there,
making it clear the 2 classes are closely related and are only meant to be
used together.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

This will allow HdySwipeGroup to get the swipeable from signal handlers.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

This isn't needed for now, but will allow to simplify the API later.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

It was just completely wrong.

1. The initial current_pad value was the right edge of the visible child.
2. Despite that, we went from the last child to the visible one and not the
   other way.
3. We decrement current_pad instead of incrementing it, matching the list
   traverse direction.

This already sounds like it will break horribly, but we also had a bug
balancing all of that:

4. We decrement current_pad by 0 instead of the proper child width, because
   we do it before the width is set.

This leads to all of the end children getting the same x coordinate,
overlapping each other.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>

There's no reason to invert every single usage of current_pad.

Signed-off-by: Alexander Mikhaylenko <alexm@gnome.org>