Update application.py

[elegantiron]

fixes type hinting to match the returned properties

fixes #2525

[pushfoo]

Although it may seem counter-intuitive, the float option may be more correct:

1. Mac uses float pairs for their screen locations (example)
2. Other platforms may as well

This affects future mobile and web support plans as well, but it's a long-standing issue which affects pyglet.

[elegantiron]

Although it may seem counter-intuitive, the float option may be more correct:

Personally, I just want my type checker to chill out; I don't care which is more correct.

If float is the more correct one, then should we change the __init__ functions to type hint that they accept floats?

I'm getting the following from pylance:

Argument of type "float" cannot be assigned to parameter "width" of type "int" in function "__init__"
  "float" is not assignable to "int"

And it is complaining about the following code:

self.title_section = TitleSection(0, 0, self.width, self.height)

This is a view attempting to create a section that is the same size as itself, but Pylance is unhappy that the types don't match.

[eruvanos]

Could we just allow float or int, both would work right?

[elegantiron]

That would solve my personal issue with it (type checking), and if it works for the technical side too I'm all for it.

[elegantiron]

I'm going to open a new pull request with changes to sections.py which hint that it accepts int or float