-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reparse text input after interaction #37
Comments
Type faster :-) (there is on purpose a slight delay before the input is reparsed it is not character by character). Seriously adding the , will create a new rule field (with the correct semantics, you should add the required fields to it via the menus. Essentially the text field is there for initial clean up of non-parseable stuff and to correct minor typos, it is not really conceived as a way to input a complete OH value. |
Sorry, i am not able to enter a valid rule in < 300 ms. :-)
Hm. You are right. There we need the direct parse :-| |
Above the gui is an editable text input.
Every change is reparsed and auto corrected after each char change.
For example ´08:00-12:00´
Adding a comma after it, the empty rule is detected and removed. So my new comma is killed while typing.
The text was updated successfully, but these errors were encountered: