LÖVE

Is it possible to make some sort off loadDraw() function? Where you basically just draw all your canvases that wont change during the game (like game terrain) once. (as calling the graphics module during load does not work :< )

After which u just always call your canvas in the regular draw function? Or do I go about it by overwriting the draw function after 1 cycle or something similar?

Smoggert wrote:Is it possible to make some sort off loadDraw() function? Where you basically just draw all your canvases that wont change during the game (like game terrain) once. (as calling the graphics module during load does not work :< )

After which u just always call your canvas in the regular draw function? Or do I go about it by overwriting the draw function after 1 cycle or something similar?

just do it somewhere. wherever you want. You can do it in love.load, in the first call to love.update, in the first call to love.draw, every frame (don't actually do this), even anywhere else in your main.lua or files that you require.

s-ol wrote:

Smoggert wrote:Is it possible to make some sort off loadDraw() function? Where you basically just draw all your canvases that wont change during the game (like game terrain) once. (as calling the graphics module during load does not work :< )

After which u just always call your canvas in the regular draw function? Or do I go about it by overwriting the draw function after 1 cycle or something similar?

just do it somewhere. wherever you want. You can do it in love.load, in the first call to love.update, in the first call to love.draw, every frame (don't actually do this), even anywhere else in your main.lua or files that you require.

O, I was for some reason under the impression that graphics calls didn't work outside of love.draw()
But it was probably something I just did wrong in the past.

Thanks

Smoggert wrote:

s-ol wrote:

O, I was for some reason under the impression that graphics calls didn't work outside of love.draw()
But it was probably something I just did wrong in the past.

Thanks

The only limitation there is afaik is that graphics functions don't work (or at least are extremely likely to break stuff) outside of the main thread.

The whole screen needs to be redrawn every frame, otherwise when you move away a window that covers the LÖVE window, it doesn't repaint. You can't just draw once and expect it to persist.

Drawing to the screen doesn't work outside love.draw because the default love.run clears the screen right before calling love.draw, erasing anything that was drawn before. The reason why it's cleared every frame is the above.

Does Love use just 1 OpenGL context or multiple? When we feed in our own shaders are these all put into the same context as the main Love context?

There is only a single OpenGL context. Multi-context OpenGL is kind of a mess.

pgimeno wrote:The whole screen needs to be redrawn every frame, otherwise when you move away a window that covers the LÖVE window, it doesn't repaint. You can't just draw once and expect it to persist.

Drawing to the screen doesn't work outside love.draw because the default love.run clears the screen right before calling love.draw, erasing anything that was drawn before. The reason why it's cleared every frame is the above.

He was talking about drawing static parts to canvases, then drawing them as quads unless I am the one who misunderstood.

s-ol wrote:He was talking about drawing static parts to canvases, then drawing them as quads unless I am the one who misunderstood.

Exactly

What are the advantages and disadvantages for using canvases?