Skip to content
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

Determine if rule-string entry needs a length check validation #4

Open
sfreemire opened this issue Sep 27, 2023 · 1 comment
Open
Labels
question Further information is requested

Comments

@sfreemire
Copy link
Owner

sfreemire commented Sep 27, 2023

In if event == '-ENTER_STRING-': section of Event Loop, does max length need to be validated?
Do other validations already make the use of excessive characters impossible?

statement is: elif len(values['-STRING_IN-']) > 69:

Update 11/21/23: If you paste a saved string and include the parentheses section, max length is triggered. This is actually helpful until Enhancement "Rule string entry updates #11" - "Handle pasting of space and/or paren section of saved string automatically (strip them out)" is completed.

@sfreemire sfreemire added the question Further information is requested label Sep 27, 2023
@sfreemire
Copy link
Owner Author

Now, when pasting strings that include the saved strings parenthesis section, the Rule String "Enter" event code strips that off automatically. "Rule string entry updates #11" is closed.

Currently, the 'Rule String:' field is only 60 characters wide. It can hold more characters, but there is no scroll bar. Therefore, users have to position the cursor and use the arrow keys to see the hidden characters. This is tedious, but will only happen when they enter a rule name that is more than 26 characters long.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant