Camera2D near and near and far types

[alejcas]

Hi, two related things:

1. It appears that calling Camera2D will default to near = 0.0, but calling Camera2D.from_raw_data will default to near = -100
2. near and far have float types but are set as integers by default by Camera2D.from_raw_data

I don't send a PR because I don't know if it should be 0.0 or -100.

[DigiDuncan]

Pinging @DragonMoffon, they're the ones handling Camera2D primarily.

[DragonMoffon]

For Camera2D it should be a float and -100.0 is correct.

[pushfoo]

The commit Dragon made wasn't cherry-pickable. I asked him in Discord whether it would be okay to roll into that branch. He said yes, so:

1. I redid it on my branch (0f75155)
2. It's credited to him

[alejcas]

Closing this as it's fixed now

[pushfoo]

TL;DR: I disagree since it's not merged and there will be force pushes breaking commit hashes.

It's not merged or released yet, but you can use that commit hash if you'd like assuming you mirror the branch to your repo. Btw, I strongly suggest mirroring and pinning if you want to use that branch ASAP because there will be commit hash changes.

[alejcas]

TL;DR: I disagree since it's not merged and there will be force pushes breaking commit hashes.

It's not merged or released yet, but you can use that commit hash if you'd like assuming you mirror the branch to your repo. Btw, I strongly suggest mirroring and pinning if you want to use that branch ASAP because there will be commit hash changes.

You are right, so reopening again