Thanks Boolsheet, that's very informative :-)

I might not have noticed this before as I've probably only used require when writing lua code to run in love. Any 'lua only' code I've written has been ad-hoc snippets used to solve problems for love development (or to help me learn the language).

That's because your syntax for require is wrong, if you have a file "some/file.lua", you do require("some.file"). ty, dropping the .lua extension works OK. Is this a change in love or in lua do you know? Passing the full filenames (i.e. including the file extension) to require a...

Thanks love development team! I have a quick question about paths. My main.lua typically brings in other local-directory .lua files, e.g. require "somefile.lua" but these files cannot now be found (worked fine in the previous version). How do I tell love 0.8.0 to search the local directory...

On my work PC: HP Compaq 6000 Pro, Duo E8500 CPU, 4GB RAM, Intel Express Q45/Q43 gfx (AKA 'steaming pile of junk'):

You support:
Framebuffers
Non-Po2 Framebuffers
Non-Po2 Images
Framebuffers up to the size 4096 x 4096
Power of 3 Framebuffers up to the size 2187 x 2187

thelinx wrote:Short answer, Yes.

OK, ta. I shall give that a try.

TechnoCat wrote: Submission must use LÖVE and run on OSX, Linux, and Windows

Hi there

I'm interested, but don't have access to either Linux or OSX systems to test on.

If I used nothing but 'vanilla' lua calls and the LOVE engine, can I assume that it'd work equally well on any of the above platforms?

TIA :-)

Bowler Hats or Top Hats are the superior :-)

As well as Qt, WTL (Windows Template library) is another possibility to consider. It's a CPL-licensed library written in C++ which extends the Active Template Library and provides a set of classes for UI construction, GDI objects etc. Of the libraries I've tried, I find it the simplest to work with ...

It might be worth adding that if you need to check for modifiers (or more generally, more than any one key being pressed) at 'key event time' (i.e. when a key is pressed), then as far as I understand it, you'll need to add some 'is down?' checks to the keypressed() method, e.g. noddy code: function ...

Robin wrote: D'oh! I typo'd. It should have been:

Code: Select all

if card.attribute then
	ATTR[card.attribute]() -- parentheses for function call
end

Now that is pretty neat. Good to know - thx!