Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
11 replies
Subscribers
8 subscribers
Views
5411 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
User Interface
When using a!paragraphField, we have refreshAfter: set to "KEYPRESS".
Jason Ruvinsky
Certified Senior Developer
over 9 years ago
When using a!paragraphField, we have refreshAfter: set to "KEYPRESS". We want to limit the character count in the paragraph field, which works by truncating in the saveInto, and we can provide a live character count in the instructions below, however the user may still enter additional characters into the paragraph, and they don't get cut off until the field loses focus (they tab or click outside of it). Is there any way to immediately reflect the truncated value in the paragraph field while they are typing?
OriginalPostID-142471
OriginalPostID-142471
Discussion posts and replies are publicly visible
Parents
0
Mike Schmitt
Certified Lead Developer
over 9 years ago
@sachinr: the issue jason is looking to fix, though, is a way to prevent the user from continuing to type in the text entry box after the size limit has been reached. doing the a!save as you mention does only save the first 100 characters, however it doesn't update the actual contents of the box until they've un-focused. Nothing short of disabling the box actually interrupts the user's input, and disabling is not the desired behavior here. IMHO based on current OOB capabilities, this situation will require compromise on one thing or another.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Mike Schmitt
Certified Lead Developer
over 9 years ago
@sachinr: the issue jason is looking to fix, though, is a way to prevent the user from continuing to type in the text entry box after the size limit has been reached. doing the a!save as you mention does only save the first 100 characters, however it doesn't update the actual contents of the box until they've un-focused. Nothing short of disabling the box actually interrupts the user's input, and disabling is not the desired behavior here. IMHO based on current OOB capabilities, this situation will require compromise on one thing or another.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data