Quantcast
Channel: Adobe Community : All Content - FrameMaker Scripting
Viewing all articles
Browse latest Browse all 888

Trapping "white document window"

$
0
0

Dear fiends,

You know, the last 10% are the most cumbersome ones...

With my script I get a "white document window" after opening of document files. I can not reproduce the behaviour reliably neither within FM (with menu) nor with ESTK (invoking only one function without menu). Even if the white screen appears, ESTK does not show a halt or error.

Painstaikenly repeating the actions (after a double FM-restart - see later why double) the effect may happen or not:

------------------------------------------------------------------------ ESTK, different sequence of files
Open FM
Open Simple Text
Start Script for work with Dialog C    Refresh ... script works correctly
Open Markers and tables    => white screen    Working on the markers possible (but I don't see what)    CTRL-l does not do anything    Running SetDisplay from ESTK does not change the situation    Where are we stuck?    Closing panel    Closing FM is time consuming
------------------------------------------------------------------------ ESTK, different sequence of files
Open FM
Open Markers and Tables
Start Script for work with Dialog C    Refresh ... script works correctly
Open Simple Text    Marke contents is default    Check syntax operates on marker of prev. document! (known problem)
Open Developer log    Refresh ... script works correctly
Switching documents etc all works
Open From-scratch-CS-markers    => White screen    There seems to be one C marker in there    Closing panel    Closing FM is time consuming

 

How to catch the reason for these white screens?

I can work on the document, but don't see the results...

 

Closing FM after appearance of "white document window":

Method one:

For each open document:

  • Click on X to close document, wait (15 sec) until dialog "save yes/no") appears
  • Document is visible
  • Click either Yes or No and wait again (about 5 sec)
  • Document is closed, nex one is white

Close FM with X

Nothing happens for at least 20 sec, so I click into the window which becomes white.

Click on X again => "Adobe FrameMaker is not responding"

OK => Cancel => FM disappears.

Method two:

Close FM with X and wait until the dialog "Select the files to save before closing" appears (30 sec)

OK => wait at least 10 sec, then the dialog closes

FM is still open und hence i click on X

=> "Adobe FrameMaker is not responding"OK => Cancel => FM disappears.

Why restart FM a second time before next test?

If I use the script just after a restart of FM (after the white screen happening), I get "Window can not be created" errors). Hence I need a second restart of FM. Then the script can be started again.


Viewing all articles
Browse latest Browse all 888

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>