Skip to main content
Solved

FME 2019 Visual Preview - Can it be always disabled even when workbench has an inspector?

P
Forum|alt.badge.img

I can turn off the Visual Preview after running one FMW. However when I run the workbench again the Visual Preview is checked again and the window is displayed against my wishes. It is as if it ignored my preference for having it off, or the selection gets overridden.

Now I have an Inspector object in the workbench and the Visual Preview setting stays unchecked as long as I run the workbench with it disabled or unconnected. But when it is connected or enabled the Visual Preview always presents itself even though I have unchecked it on the last run.

As a tangent, is there any way to launch the Data Inspector application and bypass the Visual Preview window? In some cases I don't want the Visual Preview to take up some of the overall window or have it take the memory/cpu to process a preview for 100,000 or so features.

Thanks,

Pete

Best answer by david_r

Try closing the Visual Preview window pane and activate the following setting:

View original
Did this help you find an answer to your question?

3 replies

david_r
Celebrity
  • david_rCelebrity
  • Best Answer
  • April 5, 2019

Try closing the Visual Preview window pane and activate the following setting:

P
Forum|alt.badge.img
  • pvaziri
  • Author
  • April 8, 2019
david_r wrote:

Try closing the Visual Preview window pane and activate the following setting:

Ah, thanks very much. I'll give that a try. BTW, do you know any practical limit of features where the Visual Preview window (and feature caching) are best to avoid (we have, worse case, over 2 million features processing). I heard there is no upper limit (perhaps other than disk space) but I can't seem to believe that from a CPU/Memory demand perspective.

david_r
Celebrity
  • david_rCelebrity
  • April 9, 2019
pvaziri wrote:

Ah, thanks very much. I'll give that a try. BTW, do you know any practical limit of features where the Visual Preview window (and feature caching) are best to avoid (we have, worse case, over 2 million features processing). I heard there is no upper limit (perhaps other than disk space) but I can't seem to believe that from a CPU/Memory demand perspective.

I don't know, I haven't used it enough yet to have an opinion on this. You may want to ask Safe support about it. If you do, please consider sharing the answer here.

Reply


Helpful Members This Week

Community Stats

31,372
Posts
118,981
Replies
39,002
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.