Return, Tab, and Enter keys are special keys that open and close any text editing objects.
Unlike Tab and Enter keys, the Return key inserts a carriage return when any text editor is opened.
However, the Return key opens any text editor without inserting a carriage return with a beep if the editor uses field editing attributes for any field with any input range option.
Additionally, carriage return is disabled for any field that has any Input Range option.
You’re correct, there is no way to include the carriage return character in an Input Range. I thought you might be able to do it using the Field Blueprint dialog, but unfortunately that doesn’t work either.
Is there any way to open an editor (not using field editing attributes) using the Return key without inserting a carriage return?
The Return key closes any single-line editor and reopens the same editor with the following issues:
1. If the initial selection is “All,” the content in the editor is replaced with a carriage return, and the first blank line of two lines is displayed.
2. If the initial selection is “at Start,” a carriage return is inserted before the content in the editor, and a blank first line is displayed.
3. If the initial selection is “at End,” a carriage return is added, and the content of the editor is displayed with a blinking cursor at the end of the line, pretending to be normal.
In all three settings, the cursor blinks before the carriage return, not after it. However, any text entered goes after the carriage return, resulting in no visible text and the inability to move the line using the down or up arrow keys.
After closing the editor in any way, the cursor will continue to blink until the window is closed. The cursor will keep blinking once the editor is opened and closed, even after the form is reopened. This seems to occur when a single-line editor contains multiple lines, indicating the editor is too short to display multiple lines.
Other than the tab key, any key you press to open an editor will insert that text. There’s no way to disable that.
The cursor blinking behavior you describe is an Apple bug that ProVUE has no control over.