Hi,
> But I thought important to test the changing behavior of the "return-key"
"You can use Events as a possible workaround to block this kind of warning." as it was mentioned by baxatob or just by disabling the log temporarily.
E.g.:
bLogState = Log.Enabled;
Log.Enabled = false;
<disabledButton>.Touch();
Log.Enabled = bLogState;
> changing behavior of the "return-key"
It might be fine for your given application, but in general I am not sure I like this approach. (And yes, I am also not fond of 'overly-smart' modern applications that set, say, interface language based on my regional settings or do any other things that I did not explicitly request to do.)
It may be not obvious for me (from what I see on the screen) whether or not the current input field is the last in the input sequence or not. Thus I might be wondered why I was navigated away. Also I may want to double-check entered values before submitting them. Or do something else before finally accepting entered data. So *my personal preference* is to be in control of what application is doing (by explicitly triggering the actions in particular) and not to wonder end-user with unexpected navigation...