So odd problem here...
First I generate all my screens on the fly from data sent to me from a server, so everything is drawn at runtime and in order (I've verified by dropping my edittexts to a map with an incrementing # as they are drawn and reading that back).
So - lets say I have a screen with 8 edittext fields on it. I start at the top. I enter my data and on the soft keyboard I hit enter/next whatever that version of android says/shows. I advance to the next field with no issues, I go down all 8 in perfect order.
IF I use a hardware keyboard (on a custom device) or a bluetooth keyboard and I hit the physical enter key on that keyboard I skip to the 3rd field down. If I use the tab key on these same keyboards the focus goes through the perfect desired tab order.
I wrote code that detects the enter pressed event, stores a map of what fields are in what order, and look at itself in that order and will manually setfocus to the proper next edittext. But even with that code (and debug showing it's picking the correct next text box) it skips down from ET1 to ET3, not ET2 like I expect....
If I use the soft keyboard on this same device it all works perfect...
Anyone seen this before?
First I generate all my screens on the fly from data sent to me from a server, so everything is drawn at runtime and in order (I've verified by dropping my edittexts to a map with an incrementing # as they are drawn and reading that back).
So - lets say I have a screen with 8 edittext fields on it. I start at the top. I enter my data and on the soft keyboard I hit enter/next whatever that version of android says/shows. I advance to the next field with no issues, I go down all 8 in perfect order.
IF I use a hardware keyboard (on a custom device) or a bluetooth keyboard and I hit the physical enter key on that keyboard I skip to the 3rd field down. If I use the tab key on these same keyboards the focus goes through the perfect desired tab order.
I wrote code that detects the enter pressed event, stores a map of what fields are in what order, and look at itself in that order and will manually setfocus to the proper next edittext. But even with that code (and debug showing it's picking the correct next text box) it skips down from ET1 to ET3, not ET2 like I expect....
If I use the soft keyboard on this same device it all works perfect...
Anyone seen this before?