Community Notice Board about flixel HOT 3 OPEN

Notice: Flixel tag on StackOverflow

Now and again, Flixel questions appear on StackOverflow.

• StackOverflow: Questions tagged with 'Flixel'

It would be wise keeping an eye on those tags and helping those people out. Helping new users out reaps great benefits, as if they loose interest in Flixel due to being stuck early on, they may drop Flixel and move on to a different library. Beginner questions are also a great indicator of what sort of tutorials we need, or what variable or method names need more documentation or need to be renamed for clarity.

And who knows, they may even find the Flixel Community fork from you helping them solve their issues?

I have it set up where I get email notifications every time someone uses the flixel tag in a question, and I would recommend you do the same.

from flixel.

Question: Should closed issues be imported from AdamAtomic's Flixel?

Now and then issues still pop up in AdamAtomic's Flixel repo that are closed for various reasons:

• [AdamAtomic/flixel] useDefaultHotKeys documented, not implemented

There are also some which are still open in his repo, but would be closed immediately if moved here since we have already fixed that issue:

• [AdamAtomic/flixel] FlxG.play() not destroying FlxSound object even when AutoDestroy flag is set
• [AdamAtomic/flixel] Error Message in flx.py

Should I import these issues into our our issue queue (for completeness' sake), or leave them?

from flixel.

I've been following questions tagged with Flixel at StackOverflow, but I never subscribed to receive emails. That's a nice tip, thanks!

Question: Should closed issues be imported from AdamAtomic's Flixel?

I think it's a good idea to import them. When we do that, the original issue will receive a "this issue was mentioned in XYZ", which will make the reader aware of Flixel Community (and the fix as well).

from flixel.