Fix a couple of issues with trim paths


Applying an external trim to a lottie group that has its own trim path
is not supported, and would cause an assert. Other Lottie viewers seem
to just ignore such constructs, so we do too.

As a minor optimization, let the parser ignore trim path elements
where the start and end values are constant 0% and 100% respectively,
since such trimming is a noop. Avoiding such trim path node simplifies
later handling.

As a driveby, fix a memory leak in the parser: shape objects that are
rejected (because of syntax errors etc) were allocated but not deleted.

Pick-to: 6.11
Change-Id: I289e8462c933632824d0399c98386f8a07d4c420
Reviewed-by: Kwanghyo Park <kwanghyo.park@qt.io>
commitf667eca126cdc6949e0b305bd2e1304e5c289a67
parent30ecb73dc15efd7117be9f44ed6da66fbe350d41
authorEirik Aavitsland <eirik.aavitsland@qt.io>
committerEirik Aavitsland <eirik.aavitsland@qt.io>
commit timeWed, 18 Feb 2026 10:35:00 +0100