Thank you for your post.
This is a graphic display difference between the Data Viewer and the contents within a field. The Data Viewer Result will only highlight the necessary characters. For example, if you used instead:
List ( "abc" ; "def" )
In the Data Viewer calculation under Mac OS X, only the first line is highlighted across the entire width of the Result box, and "def" is highlighted in the second row. If this was a Calculation field, or a field replaced by the contents of the calculation, when you highlight the contents of the entire field, both lines would be highlighted across the entire width of the field. Under Windows, only "abc" and "def" are highlighted in the Data Viewer Result.
With your example under Mac OS X, the return is highlighted across the width of the Result, but since there is nothing to display on the third line, nothing is highlighted on the third line. Under Windows, only "abc" is highlighted.
Regardless, I have forwarded this information to our Development and Testing departments as an inconsistency in display. When I receive any feedback, I will let you know.
I can select whole lines in the Data Viewer using my mouse and that's what LaRetta's screenshot is showing. Regardless, the Data Viewer in this case is correct, it's the FM field display that doesn't match what the FM calc engine is returning.
Also, List() with a trailing pilcrow is returning an odd result.**
ValueCount ( List ( "abc" ; "¶" ) = 2. A display of that field returns 3 lines, per LaRetta's screenshot.
Is 2 or 3 the 'correct' result? I don't know, but there is inconsistency between the display and the evaluation.
**Oops. List isn't the issue at all. It's trailing returns in general..."abc¶" alone returns two lines in field display but a value count of 1.
Thank you for your post.
"2" is the correct result. "abc" is the first value, and "¶" is the second value. The pilcrow (¶) character puts the cursor onto the third line. In your second example ("abc¶"), the value is 1, and the pilcrow puts the cursor onto the second line.
Thank you for following up for us. Part of my issue might also be that I recently switched from Windows to Mac. We have an interesting conversation about it here http://fmforums.com/forum/topic/90657-data-viewer-misrepresents-trailing-returns/ if anyone else is interested.
The inconsistency appears to exist across different programs within same OS as well as cross-platform. It would sure help if Data Viewer
showedcould show (if toggled) hidden characters. I shall put in that suggestion. In meantime, at least folks will know about it.
Thanks again! :-)
An option to see invisible characters is truly an excellent Idea!
i am new to filemaker..i would like to ask you one question..its not related with this topic..but its very basic related to currency, where inspector wont work..need to put some calculation..will you help me..?..should i write here or post somewhere else..?..pls guide..
thanx a lot..