forked from enlightenment/efl
evas: Fix C++ compilation
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
This commit is contained in:
parent
04d3cc4eb9
commit
60e31101a6
|
@ -661,7 +661,8 @@ abstract Efl.Canvas.Object (Efl.Object, Efl.Gfx, Efl.Gfx.Stack, Efl.Animator,
|
|||
[[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;
|
||||
}
|
||||
|
@ -671,7 +672,7 @@ abstract Efl.Canvas.Object (Efl.Object, Efl.Gfx, Efl.Gfx.Stack, Efl.Animator,
|
|||
@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 {
|
||||
|
|
Loading…
Reference in New Issue