Element bourdaries are turned on? What does this mean?

[Michael314]

Hi,

On one of my Frame 7.2 manuals, I get this error box when I print the manual.

"Element boundaries are turned on. Print anyway?"

I looked under the View menu and elsewhere but do not see anything called element boundaries. The online help said they are some kind of graphic representation of the tags. (Reminds me of Arbortext.)

Why might I be getting this error on only one file, how do I disable it, and does it have any negative effect on the printout?

Yours,

Michael F.

=======

[Russ Ward]

Michael,

Element boundaries are indeed a graphic representation of element tags. They only show up in a structured flow, otherwise having them turned on will produce no effect other than occasional warnings such as the one you received.

I'm guessing you are not working with structured content, otherwise this would all make more sense. However, you must at least be working within the structured interface of 7.2, otherwise it shouldn't be possible to get that message.

The command to control them is indeed in the View menu. Are you sure that there is no View > Element Boundaries in there? If not, it would seem that you are using the unstructured interface, in which case that message would be a real mystery.

Russ

[Michael314]

Russ,

With your comments, I fixed the problem.

I went into Frame's General Preferences and selected Structured Framemaker. At Frame's command, I shut down the app, restarted it, and opened the file in question. I saw the Elements menu and unchecked Element Boundaries. (With it turned on, I did not see any graphic tags.)

I then closed the file, set Preferences back to standard Framemaker, shut down and restarted Frame, and reopened the file. When I tried to print it , I no longer got the element boundaries error.

I have no idea how the file might have been set to use Structured Frame (may have been a previous tech. writer) but now I know how to fix the problem.

Thanks.

Michael F

=======

[Russ Ward]

Michael,

You should have never seen that message in the unstructured interface, because it isn't possible to have element boundaries. In fact, if you attempt to open a structured file in the unstructured interface, it will force you to strip all the structural information out, which make element boundaries not applicable in that case. So, it would appear that you uncovered some very strange and obscure bug, one that I've never heard of before.

My theory is that while the unstructured interface will strip out structural information, it fails to strip out that setting. That would be a bug seemingly with those symptoms. I suppose one could test this but I don't have time at the moment.

In any case, congratulations on the clever sleuthing to get it fixed.

Russ