Spot coloring text

[Kiele]

Maybe I had too much Christmas Cheer, but I can't seem to get this to work.

I'm hoping that this can be done as a Conditional Formatting, but I can't figure it out. However, I would settle for any method If not.

Here is what I would like.

Currently I have two fields (Notes, a Text field, and Char_To_Color, a number field).

I want to to enter a number into Char_To_Color, like 15, (or any number), and have the data in Notes reflect the character on 15, and 30, 45, 60, etc. be colored Red, or whatever the multiples of the number entered are. (i.e. 35 would include 70, 105, etc.).

Here is an sample of what I'm trying to say.

Char_To_Color = 15

Notes would reflect this:

The quick brow[color:red]n fox jumped ov[color:red]er the lazy dog.

TIA for any help.

Kiele

[comment]

You indicate version 8.5, yet you speak of conditional formatting, a version 9 feature. In any case, conditional formatting would apply to the entire field.

Since there can be any number of characters in Notes, this requires a recursive calculation - e.g. a custom function or a looping script. But what would be the purpose of coloring every n-th character in Notes?

[Kiele]

Hi comment, and thank you for your reply.

I set the version for question to reflect v9, but the Forum must have changed it back. I guess I'll have to change my Bio. Sorry for the confusion.

As to the purpose, I want to provide a visual to the user so that they can cut down their wordiness. If I tell them no more than 50 characters, and then they type 60 or 100. I don't want them to be expelled from the field through a validation, I would rather they see how many they are over, with a subtle hint.

Also, I figured that the Conditional Formatting was not going to work, as you say, I could only get the whole field to respond.

Thanks again kind sir for your help.

Kiele

[comment]

I don't think this can work - or work well, at any rate. Whichever method you choose, nothing is going to happen until user at least exits the field (if not actually commit the record). So it's not possible to cue the user at character 51 or so. They will go on typing until THEY think they are done - and only then can you tell them.

There have been attempts to have a script running in a loop (e.g. pause for 1 second, check the user input so far, re-enter the field, pause again), but I find it very distracting.

In any case, I don't understand why you would also want color characters #100, #150, etc., if the limit is set at 50. Shouldn't all characters beyond 50 be flagged?

BTW, from users perspective such limitation can be very annoying. As a user, I think that if I have something to say it's the application's job to take it down and keep a record of it - not tell me my style needs to be more concise.

[Kiele]

Hi comment,

Thanks for your reply.

Darn. I was hoping I had missed a calculation, script, or CF that would do this.

Loops are ugly.

It may sound like a overkill for the additional markers, but I wanted the client to be able to see the breaking point. Unfortunately, the Validation doesn't provide this feedback, it only lets you either reject the entry entirely, put you into the field for modification, or allows the extra characters.

If anyone has another idea, please let me know.

Thanks again,

Kiele

[LaRetta]

Sometimes text needs to print directly onto external forms so it is necessary to stay within bounds. Is this your need? Limiting amount of text should be based upon size of the rectangle provided on the form and not by the number of characters (which is difficult to determine exactly because of proportional fonts).

The field bounds should be the visual indicator of the amount of text allowed ... WYSIWYG. With that theory in mind, apply it here ... make your rectangle exactly the size of the form (or size you want) and the font size the same as well and put instructions below the field, such as "If the field expands, you've typed too much."

Decide how strict to be and, after they exit the field, you can have many ways of restricting/flagging them if they break the 'rule.' Anything short of the need to stay within bounds because of printing restrictions, in my opinion, would probably indicate over-control...