Still issue with Rules getting UNFORMATTED

Jaymer

Not sure exactly what causes this - happens on both Mac & PC clients.
I always use Textual view. Never switch to Standard View (except the Mac client won't remember prev. choice and always switches to Std. view)

I enter a Rule IN PROCESS TEXTUAL VIEW and have it nicely formatted & readable:
Screen Shot 2020-01-03 at 2.50.07 PM.png
And then at some point it gets turned into this - hard to read, to say the least.
I thought this was taken care of.
Maybe its because I sometimes use both clients? Anyone have this happen ONLY with PC client?
Screen Shot 2020-01-03 at 2.48.37 PM.png

customaware

I think it still happens if you change anything like a BO name or an Attribute name.

Very irritating.

Jaymer

I had one change on me tonight within 5 mins of saving it.
Only on PC client - no Mac involved.
Unsure about field name change.

Jaymer

If a Query would stay Formatted AND the Context Assistant would KEEP WORKING after you have split this onto multiple lines.
I think it works better in a Rule, but here, once you have added 1-3 hard line breaks, it gets real sketchy:

On PC, latest build, F3:
1) will not work after InstantMessage. on line 3
2) DOES work after InstantMessage. on line 4
3) will not work after ORDER BY
odd - could be better

Screen Shot 2020-01-03 at 10.28.44 PM.png

BLOMASKY

Remember, Windows uses CR LF to end a line, OSX (and Linux) uses just LF, Since you use both clients, that might be an issue.

I have never had a RULE reformatted. However, I always see a query get reformatted. I wish this would be fixed.

I understand if any attributes are added / deleted, it might break an existing query text. But if I just go in and change formatting, or Label, I wish it was not rewritten.

Just my 0.02 cents worth.

ddumas

I always add a line feed - press the enter key 🙂 where desired to make readable. I think as long as you do not break "mid word", this will work. I have not had a problem yet.
Dave