This is a known issue.
For More Information see: FM 12 preview mode issue
This is one of many acknowledged bugs that can be found in the Known Bug List thread here in the Report an Issue section of the forum.
It can also be downloaded as a database file from: https://www.dropbox.com/s/jt09b82i0xijbu3/FMP%20Bugs.zip
Thank you Phil. But i am not sure. As i stated, the bug is at least reproducible with v11 and maybe other past version.
Am i missing something ?
I cannot believe that Preview Mode never worked on Windows... or i am wrong ?
My records don't show this as reported with versions earlier than 12, but that may just mean that no one had reported it here until that point in time.
And it's not just preview mode and not just the data found inside a field. Zooming the layout or changing between the "enlarge window contents..." option can also change how text "Wraps". This created some significant havoc for me when I was working with the first two installments of the Adventures in FileMaking series as I have lots of text entered directly on the layout in order to document how to use, design and understand the function of each layout's demonstrated design technique.
As you know, my english is poor. I always may misunderstood your statements.
To be clear and basic, are you confirming that Preview Mode (that does not care about anchors and its automatic sizing*) never was reliable on Windows even on very simple situations ?
If so, can you just tell me in what a such Preview Mode can be of any help ?
* Edit : and that is well and "as expected" to me.
And i really think a TS-person answer would be much appropriated here.
If i am right, it is not a small issue but a a really nasty one.
If i am wrong, god bless us, it would be useful to inform us and tell us the key point.
Thank you for the post.
PhilModJunk is correct (thank you!) that we are aware of this issue. I reopened the original report made to Testing and Development and added your comments and example files to the original report.
Although definitely not ideal, a note on the report indicates this does not occur with layouts after some adjustments. I will try to get more information on what specific adjustments. The fact that you reproduced in a new file that was not converted is new information and also added to the report.
Fred, I just reported what I found in my database. I was not indicating whether or not the issue predates FMP 12--the earliest version found in the bug report record. I never noticed the issue in older versions, but this is usually very subtle when it happens at all so I personally may not have happened to notice.
Ever since Summary Reports could be viewed in Browse mode, I simply haven't had much need for Preview in my solutions and in the cases where I use it, such a minor difference in Wrap is not signficant. Obviously, I'm not using Preview to "check fit" in anything when I say that. If there is any chance that the text might not fit a field, I'm more likely to oversize the field and then set it to slide up in order to make sure the text is fully displayed.
Thank you very much Phil and TSFalcon. I appreciated you took time to get my points and answered me. I am also glad that the Issue was reopened since it appear it was closed previously. I secretly hoped that indeed an adjustment of layout coud let me workaround this (specific font or whatever). But obviously, if that meant to temporarily adjust the layout until the next occurrence of the bug occur, there is no luck.
Now, i feel a bit sad and perplexed since the issue possibly always been.
Here are additional examples in real life (please TSFalcon, be kind and transmit to T&D as they can understand why it is important) :
As a developer, i expect to be able to use Preview Mode to control number of pages by script. It was the way i discovered the bug : Switch to Preview Mode, Go to Last page, Get the Current Page and write it in a global field/variable. And then, i can print "1 of 2 pages". There are obviously a lot of other cases where a page control is useful, but it is the more basic one.
As a enduser, i expect to be able to… preview. Then i see "oh this paragraph's break is ugly" and ok, i make a manual adjustment of a field value and print only when the result is "as expected". Suppose the nightmare it could be if you used justified text alignment !
And both are not possible in actual state of things, i mean reliably. I would have understood if the case were very complex or font were, don't know, a bit "exotic". But it is definitely not the case here. I even not used bold nor italic in my sample file...
Thank you for the reply.
“please TSFalcon, be kind and transmit to T&D as they can understand why it is important”
I added your real life examples to the report made to Testing and Development. Once we have more information, this thread will be updated.