CEGUI (Crazy Eddie's GUI) Forums

As we know, there are 3 ways to use the animation system: pure code, Falagard looknfeel XML, and code && separate XML .

Is there any possibility that I can use it in a layout,such as:

confirmed that couldn't configure it in a layout ,
But I can't figure out why? I think it more flexible to use layout xml than looknfeel xml

being confused ....

I think the 'expected' approach would be to define the animation like you would in the animation/looknfeel xml, then reference it via code. Layouts are sort of like instantiations of the looknfeel's so you shouldn't really be defining the looknfeel in the layout

I could see it being useful to reference animations in the layout, however. Not sure if that possible at the moment, still haven't had enough time to use this as thoroughly as I'd like

Agree. It is nice to be able to assign animations to types of windows across the board, but sometimes you only want an animation applied to one instance. Right now, I think you can only do that via code; extending the layout xml to support this would definitely be beneficial. I'll send a PM to Kulik so maybe he will come and respond to this

Imagine these situations:
1.a kind of StaticImage that can fade away,and all I need is fade away over the time ;
2. another kind of StaticImage that can change its "image" property over the time
3. another kind of StaticImage that can change its size over the time .
...

Every new kind of StaticImage Animation need to be configured in the looknfeel, meanwhiles I may well use this kind of widget only once .Next time,when I need another kind of StaticImage animation,i have to create a new widget (that also
in all probability be used by only one time) . This obviously is kind of waste.

I think there certainly are use cases where this would be really useful. On the other hand, you can't alter look n feel in layouts and just allowing animations here doesn't sound right to me.

It also isn't as easy to just crudely plug the animations here, because the window would have to track the instances and definitions and not only create them (easy) but also delete them. Right now there is no way to do this and we previously agreed that CEGUI::Window shouldn't be "tainted" by animations... Look n feel tracks it's animations.

Every new kind of StaticImage Animation need to be configured in the looknfeel, meanwhiles I may well use this kind of widget only once .Next time,when I need another kind of StaticImage animation,i have to create a new widget (that also
in all probability be used by only one time) . This obviously is kind of waste.

spracle is right. Some animation behavior should not be widget type related.
But it is still a hard work to set image property if there are dozens of frames in the animation with layout support.

rockoz wrote:spracle is right. Some animation behavior should not be widget type related.
But it is still a hard work to set image property if there are dozens of frames in the animation with layout support.

thanks Seriously I can't get what kulik have said(maybe because I am new to cegui),and I still think layout support will make animations more flexible

spracle: hehe, you probably have to know a bit about internals of CEGUI to know why it isn't such an easy fix I don't want CEGUI to have separate animation loading implementations all over the place... I was thinking a bit more like providing looknfeel overrides inside layout files. But it's an evil thought... Would be a fun patch though

It's great work to build such animation system,and I appreciate what you have done very much ,kulik~~
I'm not quite familar with CEGUI,but i will work hard to get it.Now tough and fun