Can not post key event to handle menu

[ppizarror]

Can not post key event to handle menu

[ppizarror]

Sometimes the key events does not correspond to the keyboard events, so I added the method check_key that verify KEYDOWN is valid. For testing purposes you can raise an KEYDOWN event by adding 'test' to the dict:

pygame.event.Event(pygame.KEYDOWN, {"key"=pygame.K_DOWN, "test"=true})

pygame-menu/test/_utils.py

Lines 114 to 150 in 1e40ec7

	def key(key, char='', inlist=True, keydown=False, keyup=False, testmode=True):
	"""
	Create a keyboard event.
	:param key: Key to press
	:type key: int
	:param char: Char representing the key
	:type char: basestring
	:param inlist: Return event in a list
	:type inlist: bool
	:param keydown: Event is keydown
	:type keydown: bool
	:param keyup: Event is keyup
	:type keyup: bool
	:param testmode: Key event is in test mode
	:type testmode: bool
	:return: Event
	:rtype: pygame.event.Event
	"""
	if keyup and keydown:
	raise ValueError('keyup and keydown cannot be active at the same time')
	if keydown == keyup and not keydown:
	raise ValueError('keyup and keydown cannot be false at the same time')
	event = -1
	if keydown:
	event = pygame.KEYDOWN
	if keyup:
	event = pygame.KEYUP
	event_obj = pygame.event.Event(event,
	{'key': key,
	'test': testmode,
	})
	if len(char) == 1:
	event_obj.dict['unicode'] = char
	if inlist:
	event_obj = [event_obj]
	return event_obj

[ppizarror]

In some cases if you press a key too fast and release it the event state of pygame stills recognizes the last pressed key as pressed (the KEYUP is ignored). That bug was very common in TextInput widget

[ppizarror]

If you want we can rename 'test' to another clearer name

[anxuae]

Ok for me, I understand now the reason. I will use the key test for my custom event.
The name is ok, see in your test why you call it like that.

Thanks