I am having issues with the Text Editor object. It continue to blink an insertion point even while I have other text boxes active and receiving text. The object also does not seem to respect a minimum height which causes me to undesirably sometimes have entering text wrap to a 2nd line when I want only 1 line of entry.
Ideas?
Perhaps you could describe your situation with more detail?
Panorama X does allow more than one text box to be active. However, only one text box can be active per window, and only the text box in the topmost window will have a blinking insertion point.
The blinking insertion point is actually driven by Apple’s code. As far as I can see there can be only one blinking insertion point on your computer at a time. It doesn’t matter what application you are running, there can be only one blinking insertion point.
Huh? There is no such feature as a minimum height for an object. You can set a minimum window height, is that what you are referring to?
You can set the line breaks to Don’t Wrap.
See ‘Reference Fig:’ box and ‘Page’ box.
Re object height. It used to be that I could drag a text box up and it would always then bounce back to the minimum height that 1 line of text would represent, thus ensuring that my text boxes were not going to accidentally allow a text wrap to a 2nd line. Now I can drag the size of a text box shorter than a full line of text and that only causes more work to find that sweet spot where it is 1 line of text high.
I’ve always found it to be a big help to have text in any text object as I adjust it. Using text with Caps and ascenders always ensures that my line heights are exactly right for as many lines of text as I intend to allow.
For multi-line text boxes, that is a method that does ensure that we get the look and feel that we need. But for those times that we want a single line, it was always handy to have the ability to drag all the way too small and have the text box then snap back to the single line height as we never want less than a single line height.
I can’t imagine how this could happen. I would like to investigate this further, to do that I will need a copy of the database, and an exact description of how you got it into this state. What happens if you press a key at this point? Does it go into Reference Fig, Page, or neither?
Sorry to say that I can’t find the solution for this multiple blinking cursors in Text Editors. Would you please remind me of the fix?
I can only refer you back to my reply in February 2024. I have no idea how you can get more than one blinking insertion point, so I don’t have any fix to remind you of. The blinking is controlled by Apple’s code, and as far as I know it is impossible to have more than one blinking insertion point per computer.
If the editors are for text fields or variables, the blinking cursors for inactive editors indicate that carriage return insertion has occurred inadvertently for single-line fields or variables.
I was just about the ask this question after accidentally deleting the contents of a text field (via a text editor object) for the 999th time. (It’s way too easy too delete data when trying to add to the text in an existing text editor object )
Can anyone else duplicate this blinking cursor in the first Text Editor box?
Can anyone else duplicate this blinking cursor
As I told Robert in a private email, I only get one blinking cursor. As soon as I click in the Server Database Name the blinking in the Auto Unlock field stops.
accidentally deleting the contents of a text field
I just verified that if you set the Initial Selection option to at End then pressing the Return key does NOT delete the contents of the field.
The tab key does not close the editor, and the cursor continues to blink even after it is closed by clicking outside the box.
Except for the initial selection of “All,” the Return key does not delete the contents, but it adds a carriage return. This behavior is not problematic for multiple-lined editors, as the carriage return is visible. However, it causes issues for single-lined editors. For the initial selection of “at End,” the cursor appears to blink normally, but the Return key has already added a carriage return. Unless the editor is tall enough to display multiple lines or a vertical scroll bar is enabled, the cursor cannot move down, resulting in the cursor remaining in the first line. Consequently, any keys entered at this point are hidden in the second line. Conversely, for the initial selection of “at Start,” the contents appear to be removed, but they are actually hidden in the second line.
Are saying that you can duplicate the continued blinking of a cursor in a Text Editor box after moving on to another object?
Yes! It is not just the tab key, but also the return key does the same. Looks like no termination keys are checked for the editor, so both the return and tab keys are entered in the editor causing the cursor blinking even after the editor is closed. Looks like inactive editors also display blinking cursors when content cannot be fit, and word wrap or character wrap is enabled.
Thank you for your response. Now if we can find others that experience this multi blinking Text Editors, perhaps we can find the cause. Some would say it is an extension on my system but I’m sure I’ve seen this on other client systems as well.
I posted about this last April 30 and included a screen shot showing 3 insertion points. This is unacceptable.
Jim is unable to replicate this so we need all the info we can. For reference, that previous post was Multiple fake insertion points
What we need to find is a way to allow someone else to replicate it. Can anyone do a sequence of events such that they can ‘make it happen’? Can that then be simplified and then submitted as an example to ProVUE via email with you believing that it will happen upon receipt?
