I guess it's not LÖVE or lua, no. What I wanted to do is to make it easier to use the tool I'm creating, by dragging and dropping a file or directory into its window. Also, later I've realized how cool this would be with the LÖVE player itself! Just starting LÖVE and dragging a .love file into it, n...

Okay, thanks!

Hello!

Just a quick question, is it possible somehow to drag a file or folder from e.g. a file browser, and drop it in a LÖVE window, and to catch this as an event and an argument in LÖVE?
I didn't find anything on this topic.

Thanks in advance!
Cheers,
easy

Nitpick, but easy82's code is creating a new closure for that update function every loops. Yes, it's really convenient, this way I could put it into a module nicely. What is the problem with that? I'm always willing to learn something new. Of course, there's a huge number of problems with doing it ...

10ms is probably a bad value though, since that's 100fps, which most people are not going to have (because of vsync), therefore you'll be getting weird framerate dips every once in a while (whenever you do a double update to correct for this), I'd recommend going no higher than 60fps. Good advice! ...

I've got a really neat trick I've learned over time, and it's also really simple. Here is the main idea: 1. You always draw everything whenever you can. 2. You use a fixed timestep on your update function(s). So the way I do this is the following: - Say my fixed timestep is 10ms. - No matter if more...

Hey everyone, I just wanted to say that LÖVELINESS v0.2.0 is now available on the Chrome Web Store! Some features: * persistent storage! (i.e. writing files/directories via love.filesystem.* works now) * loading links via the context menu: right-click on a link, and choose "Open with LÖVELINES...

Wow! This is an outstanding LÖVE game! Congratulations! :D I love the graphics, the music and the sounds, they all add a nice retro feeling to the game. The game idea is also very good, reminds me classics like Donkey Kong. The execution is very smooth, I can see how much effort you guys put into th...

Not sure I fully understand what you're asking, but for 1. I would always store a "pointer" to a table of metadata (that table might also be the object it is describing) and I'd but some type information in there. Usually something like: local data = { player=true, blocking=false, object=...

Hi! 1. I'm trying to figure out what is the best way to identify a collider object when using the physics callbacks. How do you guys do it? A) Set the UserData attribute to store 'player.one', 'player.two', 'block.simple.22', 'block.triggered.56', etc. Then I could parse the string, and use it to id...