Fix broken unicode len checking in examples/textinput.py

[zaphodikus]

On Win32, the ENTER key handling completely was defeated for some reason, so chatbox entering of text does not do anything since the unicode for ENTER is '\r' and is length 1, not zero.

[Starbuck5]

The example works on pygame 2.0.0, but not on 2.0.1.

With this example script, you can see that KEYDOWN events like enter or ctrl-c have filled out unicode attributes in 1.9.6, and in 2.0.1, but not in 2.0.0.

import pygame
pygame.init()

screen = pygame.display.set_mode((400,400))

clock = pygame.time.Clock()
while True:
    clock.tick(100)

    for event in pygame.event.get():
        if event.type == pygame.QUIT:
            pygame.quit()
            raise SystemExit

        if event.type == pygame.KEYDOWN:
            print(event)

So that's the deal with why this is broken now.

@zaphodikus Should this test for unicode field length at all?

Requesting a review from ankith26, because I think their event refactor PRs for 2.0.1 are related to this.

[ankith26]

I consider this change as a "fix" from my event refactor PRs, because the output is same as that in 1.9.6

As to this PR, it is looking good, but I feel that completely removing the event.unicode check might also be a good option

[robertpfeiffer]

I have made a new textinput example to supplant this one after my IME fix and IME docs are merged. I'll take a look at this soon.

[illume]

👍 thanks.

Since it's 1.9.6 compatible, I'm ok with this.
(Probably better to remove the len(event.unicode) bit all together.)

[ankith26]

Yeah this PR seems good to go, to me as well!
Since the original author of this PR seems inactive, should I remove the and len(event.unicode) == 1 check altogether, and then merge this?

[illume]

Since the original author of this PR seems inactive, should I remove the and len(event.unicode) == 1 check altogether, and then merge this?

I'm ok with that (and also just merging it... up to you?)