pub trait PixbufAnimationImpl: ObjectImpl + ObjectSubclass<Type: IsA<PixbufAnimation>> {
// Provided methods
fn is_static_image(&self) -> bool { ... }
fn static_image(&self) -> Option<Pixbuf> { ... }
fn size(&self) -> (i32, i32) { ... }
fn iter(&self, start_time: SystemTime) -> PixbufAnimationIter { ... }
}Provided Methods§
Sourcefn is_static_image(&self) -> bool
fn is_static_image(&self) -> bool
Checks whether the animation is a static image.
If you load a file with PixbufAnimation::from_file() and it
turns out to be a plain, unanimated image, then this function will
return TRUE. Use PixbufAnimationExt::static_image() to retrieve
the image.
§Deprecated since 2.44
Use a different image loading library for animatable assets
§Returns
TRUE if the “animation” was really just an image
Sourcefn static_image(&self) -> Option<Pixbuf>
fn static_image(&self) -> Option<Pixbuf>
Retrieves a static image for the animation.
If an animation is really just a plain image (has only one frame), this function returns that image.
If the animation is an animation, this function returns a reasonable image to use as a static unanimated image, which might be the first frame, or something more sophisticated depending on the file format.
If an animation hasn’t loaded any frames yet, this function will
return NULL.
§Deprecated since 2.44
Use a different image loading library for animatable assets
§Returns
unanimated image representing the animation
Sourcefn iter(&self, start_time: SystemTime) -> PixbufAnimationIter
fn iter(&self, start_time: SystemTime) -> PixbufAnimationIter
Get an iterator for displaying an animation.
The iterator provides the frames that should be displayed at a given time.
start_time would normally come from g_get_current_time(), and marks
the beginning of animation playback. After creating an iterator, you
should immediately display the pixbuf returned by
[PixbufAnimationIterExtManual::pixbuf()][crate::prelude::PixbufAnimationIterExtManual::pixbuf()]. Then, you should install
a timeout (with g_timeout_add()) or by some other mechanism ensure
that you’ll update the image after
[PixbufAnimationIterExtManual::delay_time()][crate::prelude::PixbufAnimationIterExtManual::delay_time()] milliseconds. Each time
the image is updated, you should reinstall the timeout with the new,
possibly-changed delay time.
As a shortcut, if start_time is NULL, the result of
g_get_current_time() will be used automatically.
To update the image (i.e. possibly change the result of
[PixbufAnimationIterExtManual::pixbuf()][crate::prelude::PixbufAnimationIterExtManual::pixbuf()] to a new frame of the animation),
call [PixbufAnimationIterExtManual::advance()][crate::prelude::PixbufAnimationIterExtManual::advance()].
If you’re using PixbufLoader, in addition to updating the image
after the delay time, you should also update it whenever you
receive the area_updated signal and
[PixbufAnimationIterExtManual::on_currently_loading_frame()][crate::prelude::PixbufAnimationIterExtManual::on_currently_loading_frame()] returns
TRUE. In this case, the frame currently being fed into the loader
has received new data, so needs to be refreshed. The delay time for
a frame may also be modified after an area_updated signal, for
example if the delay time for a frame is encoded in the data after
the frame itself. So your timeout should be reinstalled after any
area_updated signal.
A delay time of -1 is possible, indicating “infinite”.
§Deprecated since 2.44
Use a different image loading library for animatable assets
§start_time
time when the animation starts playing
§Returns
an iterator to move over the animation
Dyn Compatibility§
This trait is not dyn compatible.
In older versions of Rust, dyn compatibility was called "object safety", so this trait is not object safe.