You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I encountered a similar issue when trying to load a GIF file using @pixi/gif with PIXI.js version 7.x. The initial method I tried failed to load the GIF, returning null, so I attempted another approach. While the second method successfully loaded the GIF, it raised errors whenever the mouse was moved in and out of the canvas area.
Method 1 (Not Working)
Here is the initial method I tried, but the GIF returned null:
The console.log('loadGif.image', image) statement prints null.
Method 2 (Working but with Errors)
I then tried the following method, which successfully loads the GIF but raises errors when the mouse moves in or out of the canvas:
The GIF loads and displays correctly, but moving the mouse in and out of the canvas area causes errors. Below is the error message screenshot:
Steps to Reproduce
Install @pixi/gif version 2.1.1 and PIXI.js version 7.x.
Create the above function to load a GIF file.
Observe the console output after calling the loadGif function. The image is null instead of an expected PIXI.Texture or PIXI.Sprite.
Expected Behavior
The Assets.load function should load the GIF and return a valid PIXI.Texture or PIXI.Sprite, which can be added to the app.value.stage.
Actual Behavior
The Assets.load function returns null, making it impossible to add the GIF sprite to the stage.
Additional Information
PIXI.js version: 7.x
@pixi/gif version: 2.1.1
Environment: Working on a Vue 3 application, with the following setup in the onMounted lifecycle hook.
Questions
Is there a specific method I need to use to correctly load a GIF file with @pixi/gif?
1.Are there additional configurations or imports required that I might be missing?
2.Any assistance or guidance you can provide on this issue would be greatly appreciated!
3.For Method 2, what causes the errors when the mouse moves in and out of the canvas, and is there a way to resolve this?
Thank you!
The text was updated successfully, but these errors were encountered:
Hello,
I encountered a similar issue when trying to load a GIF file using @pixi/gif with PIXI.js version 7.x. The initial method I tried failed to load the GIF, returning null, so I attempted another approach. While the second method successfully loaded the GIF, it raised errors whenever the mouse was moved in and out of the canvas area.
Method 1 (Not Working)
Here is the initial method I tried, but the GIF returned null:
The console.log('loadGif.image', image) statement prints null.
Method 2 (Working but with Errors)
I then tried the following method, which successfully loads the GIF but raises errors when the mouse moves in or out of the canvas:
The GIF loads and displays correctly, but moving the mouse in and out of the canvas area causes errors. Below is the error message screenshot:
Steps to Reproduce
Install @pixi/gif version 2.1.1 and PIXI.js version 7.x.
Create the above function to load a GIF file.
Observe the console output after calling the loadGif function. The image is null instead of an expected PIXI.Texture or PIXI.Sprite.
Expected Behavior
The Assets.load function should load the GIF and return a valid PIXI.Texture or PIXI.Sprite, which can be added to the app.value.stage.
Actual Behavior
The Assets.load function returns null, making it impossible to add the GIF sprite to the stage.
Additional Information
PIXI.js version: 7.x
@pixi/gif version: 2.1.1
Environment: Working on a Vue 3 application, with the following setup in the onMounted lifecycle hook.
Questions
Is there a specific method I need to use to correctly load a GIF file with @pixi/gif?
1.Are there additional configurations or imports required that I might be missing?
2.Any assistance or guidance you can provide on this issue would be greatly appreciated!
3.For Method 2, what causes the errors when the mouse moves in and out of the canvas, and is there a way to resolve this?
Thank you!
The text was updated successfully, but these errors were encountered: