You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this point, the manual frequency selection controls need some additional tuning. For instance, when entering the EditText box, the 'set frequency' Button is not immediately enabled now. This is good, proper behavior, as far as I'm concerned. However, the button does not activate until the user has entered a numeric value, and pressed 'enter', on the touchscreen. This is not the behavior that we want. I'm not sure if it's possible to parse the edit text's value before it's been entered, but that would be best... IE: dynamic enabling, and disabling, of the button, depending on the value (20 <= val <= 20k). If this is not possible, the button at least needs to be active after starting to enter numeric values. Then the validation can be processed once the set frequency button is pressed.
There are other issues, #21, and #19, that will be closely related to the code in this issue, as well. I believe that #22 is closed, in working with this segment, though.
The text was updated successfully, but these errors were encountered:
At this point, the manual frequency selection controls need some additional tuning. For instance, when entering the
EditText
box, the 'set frequency'Button
is not immediately enabled now. This is good, proper behavior, as far as I'm concerned. However, the button does not activate until the user has entered a numeric value, and pressed 'enter', on the touchscreen. This is not the behavior that we want. I'm not sure if it's possible to parse the edit text's value before it's been entered, but that would be best... IE: dynamic enabling, and disabling, of the button, depending on the value (20 <= val <= 20k). If this is not possible, the button at least needs to be active after starting to enter numeric values. Then the validation can be processed once the set frequency button is pressed.There are other issues, #21, and #19, that will be closely related to the code in this issue, as well. I believe that #22 is closed, in working with this segment, though.
The text was updated successfully, but these errors were encountered: