Efl.Animation and Efl.Canvas.Object need each other, and introduce a
cyclic dependency. Eolian doesn't complain... but C++ fails to compile,
as one header must be included before the other, and vice-versa.
Do we have other cyclic dependencies? I remember we lifted the
limitation in eolian itself, but can't remember exactly how it should be
handled...
Ping @q66 @felipealmeida
[[Set the $animation which starts when the given $event_name happens to the object.]]
params {
@in event_type: Efl.Animation.Event_Type; [[The event type the given $animation is set for.]]
- @in animation: Efl.Animation; [[The animation which starts when the given $event_name happens to the object.]]
+ @in animation: Efl.Object /* FIXME: Efl.Animation */;
+ [[The animation which starts when the given $event_name happens to the object.]]
}
legacy: null;
}
@in event_type: Efl.Animation.Event_Type; [[The event type the given $animation is set for.]]
}
legacy: null;
- return: Efl.Animation @warn_unused;
+ return: Efl.Object /* FIXME: Efl.Animation */ @warn_unused;
}
}
implements {