Olivier Goffart 975abf3c42 Don't steal the x and y properties for dummy parents ... Parents surch as Opacity, Clip, and co, used to steal the x and y property of their children, making the property not what they ought to be. Now that we refactored recently the code so that geometry need not to be always linked to a property of the same name, we can dissociate the x and y property of these generated elements and their content so that the actual "x" property of the former elementstay some value, despite its relative item property is now 0. Had to change a bit of code that was still assuming a literal "height" or "width" or "y" or "x" property that no longer worked when the geometry is dissociated from its property Fix #1072		2023-10-21 07:30:46 +02:00
..
optim_passes	WIP: Add item_geometry to the ComponentVTable	2023-09-13 16:08:37 +02:00
expression.rs	janitor: Fix clippy errors about wrong clone implementations	2023-09-20 20:23:38 +02:00
item_tree.rs	WIP: Add item_geometry to the ComponentVTable	2023-09-13 16:08:37 +02:00
lower_expression.rs	Compiler: be more granular for checking for explicit layout constraint	2023-10-12 12:55:00 +02:00
lower_to_item_tree.rs	Don't steal the x and y properties for dummy parents	2023-10-21 07:30:46 +02:00
pretty_print.rs	Change item indices from usize to u32	2023-09-12 08:53:58 +02:00