Expand my Community achievements bar.

SOLVED

Text Editing Problem

Avatar

Level 2

I have a problem.

I'm new to LiveCycle - and everything (save for periodic crashes and odd interface issues) has been great - but I've since run into this serious problem:

I can delete things from a text object, change the font, color, etc  - but I cannot edit the text or add new text no matter what I try. It's clearly still accessible by the program, not locked under the edit menu,  and not responding to a right-click - edit text.

Have you guys run into this before? How can I fix this? It seems so simple.

Thanks in advance!

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Basically the text object could not flow any larger because the object contained a bunch of line-feed characters (enter key) at the end of the text stream. By removing the line-feed characters the text object became editable again.

Steve

View solution in original post

5 Replies

Avatar

Former Community Member

Are you running Designer 7.x or 8.0 by chance?

Do you mean objects of type 'Text Field' or 'Text'?

Steve

Avatar

Level 2

I'm running version 8 - Type Text.

Thanks for the quick response.

Avatar

Former Community Member

Can you forward the form to stwalker.adobe@gmail.com?

Steve

Avatar

Correct answer by
Former Community Member

Basically the text object could not flow any larger because the object contained a bunch of line-feed characters (enter key) at the end of the text stream. By removing the line-feed characters the text object became editable again.

Steve

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----