Split this into allowing TABS and/or allowing Arrow keys...DT Picker controls need Arrow Keys for adjusting values, but don't process TABs so they could still be used to navigate to next/previous controls...or if you are adding these to the toolbar, just remember to make them work this way.
I'm still confused why the arrow keys even navigate to other controls though...I've never seen an app that did that and it messes with other controls besides DT Picker like sliders, etc...maybe FF could only process arrow keys for Option groups?
Adding it to the check in the generated code's KeyDown message processing also works:
CASE "COMBOBOX", "LISTBOX", "SYSLISTVIEW32", "SYSTREEVIEW32", "SYSDATETIMEPICK32"
Quote from: Roger GarstangI'm still confused why the arrow keys even navigate to other controls though...I've never seen an app that did that and it messes with other controls besides DT Picker like sliders, etc...maybe FF could only process arrow keys for Option groups?
If I remember correctly, I think that I did it that way because that was the way that Visual Basic handled it. I can certainly change the behaviour though.
Quote from: Roger GarstangAdding it to the check in the generated code's KeyDown message processing also works:
CASE "COMBOBOX", "LISTBOX", "SYSLISTVIEW32", "SYSTREEVIEW32", "SYSDATETIMEPICK32"
Thanks Roger, I have made the change.