07859: jupace: Natural keyboard playing up

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
07859	DIP/Input	Minor	Always	Jan 27, 2021, 14:53	Jan 28, 2021, 04:04

Tester	Robbbert	View Status	Public	Platform	MAME (Official Binary)
Assigned To		Resolution	Suspended	OS	Windows 10 (64-bit)
Status [?]	Closed			Driver	cantab/jupace.cpp
Version	0.228	Fixed in Version		Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	07859: jupace: Natural keyboard playing up
Description	When using the natural keyboard, the shift keys do strange things.
Steps To Reproduce	>mame64 jupace -natural Hold left shift, hit a key - nothing happens. Hold left shift, hold a key for a while, let keys go - when Shift is released, suddenly a whole bunch of letters appear Hold right shift, hit a key - nothing happens. Hold right shift, hold a key for a while - does the same as left shift. Right shift is supposed to produce symbols, but that is now impossible.
Additional Information	Sometimes if you hit a bunch of keys with shift you might get a random capital letter appear. --- 'mbee' also has a natural key problem where lower-case will not appear, yet uppercase (with the shift key) works fine. Like the jupace, this was all working fairly well a few months back.
Github Commit

Flags
Regression Version
Affected Sets / Systems	jupace

Attached Files

No.18409 cuavas Administrator Jan 27, 2021, 19:32	Are you sure it's not just releasing the key before the emulated machine registers it? The natural keyboard manager is posting input events correctly.
No.18410 Robbbert Developer Jan 27, 2021, 21:05 edited on: Jan 27, 2021, 21:05	I did turn on logging in natkeyboard.cpp and the uppercase registered correctly, but symbols shift was being interpreted as normal shift (which is incorrect). Nevertheless, the uppercase was not making its way to the actual machine, but I couldn't figure out the path that takes.
No.18411 Robbbert Developer Jan 27, 2021, 21:23	Once I finally found my natural keyboard spreadsheet, I found that jupace was problematic even then. So, let's just close this, even though I think something weird is going on.
No.18412 cuavas Administrator Jan 28, 2021, 04:04	I think the issue is just that the one-size-fits-all delay in the natural keyboard manager doesn’t work well with this machine.