Hey no worries (even if you necroposted the same thread again after 2 years), it's not like the forum police will come after you.
But seriously, please stop doing that.

Apart from you using a file hoster that doesn't support hotlinking and probably infects computers with viruses, i don't see the issue in your image; is your issue related to the text not having the correct writing direction, or to the glyphs not using their correctly connected forms? Edit: From what...

It shows it for a split second because i removed the sleep command; with it, the image would indeed show for 3 seconds, after the initial flash and transparency, but again, that's irrelevant. And actually, every löve program behaves like this for me when the window is created.

I attached the gif i captured; looks like it can't be avoided this way.

Tried that, nothing different; i could try to capture a gif with licecap of how it's on my end?

Also, if this behaviour of SDL can't be mitigated, i might look into spawning the window outside the desktop area, and moving it back after 3 secs or so, so that that init thing won't show at all.

Apologies, i found the context a bit lacking so i was confused about your first answer; That said, i tested your solution, and on my end, the initial SDL window with the initialized contents (ie white, or apparently black on OSX, according to slime) won't "replace" that startup phenomenon, (and in m...

Um, you shouldn't do that? newImage is wasteful like that?
Also what note about love.run? and where's the explanation that that code looks like love.run's part, and you shouldn't even need to call clear nor present?
What's happening :V

In that case, it might be that because of some inexplicable design decision on löve's part, you can no longer use love.graphics functions without creating an actual graphical window (even if some functions did work without it previously); i'm not sure on this one, though i do remember something like...

A quick look at Config_Files will tell you that you're missing at least two things; t.modules.window = true and t.modules.graphics = true.

math.floor(x + .5) (and math.ceil(x - .5) for negative numbers) helps with rounding issues where x might be close enough to some number point 5 decimal, e.g. 1.5 should be rounded towards 2, but math.floor(1.5) will floor it to 1.0 instead, because that's what it's supposed to do; 1.5 + .5 = 2, so t...