Implement scaling for FlxTilemapExt

[DalekCraft2]

FlxTilemapExt works with FlxTilemap's scale field properly now.

I have not made many changes to FlxTilemapExt's doc comments, but I probably will make more changes to them if I am given permission.

[Geokureli]

FYI, for future changes, know that having the functional changes mixed in with the formatting changes makes this much more tedious to review, either keep them in separate commits or preferably in separate PRs.

This is a small 20-50 line, high-priority change, made into a 250 line change for things I consider low priority, I could have probably tested the functional changes and had this approved in a half hour, now it'll likely not get done for a couple of days

[Geokureli]

Just really want to restate what I said in HaxeFlixel/flixel#2763:

If you make a change to some code to fix a bug or add a feature, you can change the formatting, comments, documentation of that method, if the file is small and isolated, you might want to make similar changes to the other methods.

Just because you make a change in a file, that does not give you license to completely rewrite and/or reformat the entire file. Only edit the methods you are ALREADY changing for functional reasons if you want to reformat an entire file, make a separate PR for that change. I would not consider FlxTilemap.hx to be small. I meant like 4 or 5 methods, max

[DalekCraft2]

I could undo the latter two commits, if you'd like.

I won't do it unless you say I should, though, because you may be already looking through the changes right now, and I don't want to make you confused and make you need to start over.

[Geokureli]

I could undo the latter two commits, if you'd like.

Nah

Same question as flxweapons, do you have a small test file i can use? I assume its quench, so ill make my own test when i have a chance.

[DalekCraft2]

Yeah, it was Quench. It should be pretty easy to make a test, though.

[Geokureli]

hold of on changes I'm gonna try some things, I have questions, tho

[DalekCraft2]

For everything what you questioned, I copied the code from FlxTilemap because I figured it probably had better and more up-to-date code than FlxTilemapExt.

_{If it can be simplified, though, that'd be great; it would mean that second TODO comment at the top of the file could be removed.}

[Geokureli]

Cool, I'll just make similar changes to FlxTilemap in another PR. next time please explain changes like this in the PR description otherwise I'l assume they're some style preference you have

[Geokureli]

I'm done making changes, anything you want to add?

[DalekCraft2]

Where exactly is FlxObject.separate() called in the overlapsWithCallback() function? I don't see any usage of it, and I don't know why it would be mentioned if it is not used.

[Geokureli]

Where exactly is FlxObject.separate() called in the overlapsWithCallback() function? I don't see any usage of it, and I don't know why it would be mentioned if it is not used.

excellent point, lol. 1 more edit coming

[Geokureli]

sorry, I was sick for these last few days. any more comments or concerns, @DalekCraft2 ?

[DalekCraft2]

None right now. I can always bring them up in some other PR if I think of any.

[Geokureli]

Thanks!

Also note of similar changes being made to FlxTilemap in https://github.com/HaxeFlixel/flixel/pull/2734/files