summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* widget: Remove allocation memberwip/baedert/transforms6Timm Bäder2019-02-143-70/+39
| | | | x and y are always 0 now, so only save the size.
* widget: Fix get_allocationTimm Bäder2019-02-141-2/+2
| | | | | This was always returning 0/0 as the position, breaking things like the emoji chooser.
* widget: Remove _gtk_widget_get_allocationTimm Bäder2019-02-144-19/+12
| | | | | | Getting the allocation is kind of discouraged until we have figured out what exactly we need to expose, so stop having an internal function for it. Most of the calls should be replaced by gtk_widget_compute_bounds.
* flowbox: Implement get_child_at_pos properlyTimm Bäder2019-02-141-17/+5
| | | | | | With transforms in the mix, checking if the coordinate is inside the widget "allocation" makes even less sense. Just use gtk_widget_pick() and walk up until we find a GtkFlowBoxChild.
* testsuite: Disable more pick() testsTimm Bäder2019-02-141-4/+8
| | | | This doesn't work without a toplevel window...
* Add & use GTK_CSS_AFFECTS_TRANSFORMTimm Bäder2019-02-143-2/+9
|
* Fix shadowing warningsTimm Bäder2019-02-141-4/+0
|
* widget: Apply CSS transform in size_allocate_transformedTimm Bäder2019-02-141-0/+27
|
* csstransformvalue: Export is_noneTimm Bäder2019-02-142-2/+2
| | | | We'll use it later in gtkwidget.c
* css: Add transform style propertyTimm Bäder2019-02-142-1/+9
|
* Add flipping testTimm Bäder2019-02-142-0/+210
|
* widget: Fix queue_allocate on transformed widgetsTimm Bäder2019-02-141-1/+5
| | | | | If we just use gtk_widget_size_allocate here, we lose previously set transformations.
* Add shrinking test caseTimm Bäder2019-02-142-0/+185
|
* gl renderer: Remove an incorrect commentTimm Bäder2019-02-141-5/+3
| | | | Quite some other nodes use more than one quad these days.
* gl renderer: Flip the framebuffer when dumping itTimm Bäder2019-02-141-3/+14
|
* gl renderer: Fix offscreen-drawn transform nodesTimm Bäder2019-02-141-16/+35
| | | | | | We need to vertically flip them if they are indeed drawn offscreen, like everything else. Also use the child bounds for the offscreen texture, because that's what we draw offscreen.
* testwidgettransforms: Set transformation in size_allocateTimm Bäder2019-02-141-56/+34
|
* widget: Only push a transform if we need toTimm Bäder2019-02-142-2/+11
|
* testwidgettransforms: Add toggle for pickingTimm Bäder2019-02-141-3/+28
|
* Add size_allocate_transformed to the docsTimm Bäder2019-02-142-0/+13
|
* testformentry: Pass transform in size_allocateTimm Bäder2019-02-141-10/+10
|
* compute_bounds: Add preconditionsTimm Bäder2019-02-141-0/+4
|
* testsuite: Fix translate test for size_allocate changesTimm Bäder2019-02-141-3/+4
| | | | | gtk_widget_set_transform is still a hack that will eventually go away but it's also still useful for testing.
* widget: Handle position in transformation matrixTimm Bäder2019-02-144-184/+246
| | | | Most unoptimized version so far.
* Add form entry testTimm Bäder2019-02-142-0/+230
|
* tests: Add some transform test with CSS valuesTimm Bäder2019-02-142-47/+72
|
* widget: Fix translate_coordinates for CSS valuesTimm Bäder2019-02-142-28/+70
| | | | | As well as compute_bounds. In these cases, we need to consider the CSS values (margin, border padding) specially.
* widget Add gtk_widget_get_transformTimm Bäder2019-02-142-0/+15
|
* Add test for widget transformsTimm Bäder2019-02-142-0/+344
|
* Add picking/translation/compute_bounds unit testsTimm Bäder2019-02-142-0/+398
|
* widget: Consider widget transformations in translate_coordinatesfTimm Bäder2019-02-141-13/+16
|
* widget: Look at transform in compute_boundsTimm Bäder2019-02-141-20/+66
| | | | | We now return an axis-aligned bounding box for the given widget, in the coordinate space of the target widget.
* widget: Make translate_coordinatesf publicTimm Bäder2019-02-142-7/+8
|
* widget: Don't use compute_bounds in _real_containsTimm Bäder2019-02-141-46/+62
| | | | | compute_bounds will look at the widget transformation and return an axis-aligned rectangle containing the given widget.
* widget: Care about transformation in translate_coordinatesfTimm Bäder2019-02-141-10/+39
|
* widget: Use translate_coordinates in pick()Timm Bäder2019-02-141-3/+4
| | | | | In case converting the coordinate into the child coordinate space consists of more than just a translation.
* widget: Add gtk_widget_set_transformTimm Bäder2019-02-142-0/+13
| | | | | This might not stay until the end but for now it's good enough to test widget transforms.
* widget: Push transform node when neccessaryTimm Bäder2019-02-141-1/+8
|
* widget: Add transform matrixTimm Bäder2019-02-142-0/+4
| | | | Unused for now.
* assistant: Add a pages propertyMatthias Clasen2019-02-132-1/+114
| | | | | This is mainly useful to make the page objects accessible in the inspector.
* Exempt "pages" properties from defaultvalue testMatthias Clasen2019-02-131-1/+6
| | | | | | | Ironically, these properties are too good - they always give you a proper value, which is unfortunately different from the declared default value, which is NULL. So, don't check these.
* inspector: Support list model propertiesMatthias Clasen2019-02-131-0/+56
| | | | | This is just a very quick hack for a property editor that allows to drill down into list models.
* stack: Add a pages propertyMatthias Clasen2019-02-131-0/+8
| | | | This makes the list model available in the inspector.
* inspector: Make object property inspection work againMatthias Clasen2019-02-131-0/+1
| | | | This was lost when porting to GtkListView.
* inspector: Add an api to activate an objectMatthias Clasen2019-02-132-1/+11
| | | | | | | | This will be used to make object property inspection work again. This will be used to make object property inspection work againn
* inspector: Fix selecting objects with a next tabMatthias Clasen2019-02-132-2/+2
| | | | This was causing criticals.
* Add a missing iconMatthias Clasen2019-02-135-2/+0
| | | | | | The view-refresh-symbolic icon is used in the data list of the inspector. So ship it in gtk. No need to have it in the demos, then.
* stack: Don't emit bad ::selection-changed signalsMatthias Clasen2019-02-131-5/+14
| | | | | | We have to be careful to not pass bad numbers to this signal, which was happening in cases where we have on old or new selected item.
* stack: Fix a corner-caseMatthias Clasen2019-02-131-3/+0
| | | | | | When the stack goes empty, we were failing to reset the visible_child member to NULL, causing problems later on, since we don't have a ref for it.
* stack: Don't leak a referenceMatthias Clasen2019-02-131-1/+1
| | | | | The page holds a reference to the widget, so can't just clear this pointer.