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
All of three major implementations of piston2d-graphics interface, gfx, opengl and glium, have their own empty or from_path functions to create a texture. They are basically doing the same thing: prepare memory and call CreateTexture::create.
I think these functions can be CreateTexture's provided methods, and that will boost piston's backend-agnostic feature.
There are minor differences to be discussed in current backend implementations (such as how they report errors, opengl omitting factory because it is (), or Flips in gfx vs glium, ...), but first I want to check if anyone is interested.
The text was updated successfully, but these errors were encountered:
All of three major implementations of piston2d-graphics interface, gfx, opengl and glium, have their own
empty
orfrom_path
functions to create a texture. They are basically doing the same thing: prepare memory and callCreateTexture::create
.I think these functions can be
CreateTexture
's provided methods, and that will boost piston's backend-agnostic feature.There are minor differences to be discussed in current backend implementations (such as how they report errors, opengl omitting factory because it is
()
, orFlip
s in gfx vs glium, ...), but first I want to check if anyone is interested.The text was updated successfully, but these errors were encountered: