This content has been marked as final. Show 7 replies
I don't believe it is possible.
Hi Martin, Dave,
Dave is right--you can't. You can't do it in the UI without the plug-in, so you can't do it via scripting. Very early versions of InDesign (pre 1.0) had this feature, but it's just too crazy. Think about what happens when the next text frame of an inline frame is the frame containing the inline frame. Only madness lies in that direction.
Like Dave and Ole said: you can't. But with APID and some very fancy
footwork, you can fake it...
Dave, Olav and Harbs,
thank you for the information.
Well, somethimes there are situations in which you wish you could do that.
E.g. linking from an anchored marginal note to a new textframe on the next page.
Or linking from a textframe within a table cell to a new textframe within another table cell or to a textframe outside the table.
There should be ways to prevent linking from a textframe to its parent, that's true.
But as there are ways to prevent linking from an anchored textframe to another frame I could imagine that this should be possible to be handled, too. ;-)
And as Harbs told, you can fake it.
E.g. with the overset manager (above).
And you can fake it in such a manner that if you once have linked an anchored textframe to another you can disable the plugin without loosing this feature in the linked frames (the anchored textframe has got a real nextTextFrame).
But I do understand that one could drive into a lot of problems, trying to link from a textframe within a table cell to the textframe the table is in.
Bad news for people who have to work with longer marginal notes that should hang relative to the anchor in a text line and sometimes should be continued on next page.
what happens if you round-trip such a document thru INX, or even Snippet?
at the beginning of the export (both, inx and inds) you are warned because auf overset text which really is completely shown in linked textframes by the function of the plugin.
After reopening the inx the link between a 'normal' textframe and it's overflow-textframe (created by the plugin) is intact as before. The overflow-textframe is highlighted as before (fillcolor). The same is found after placing the inds.
But what a surprise at a previously anchored textframe:
INX: the anchored textframe is empty und no longer linked with the overflow-textframe.
The text of the anchored textframe is completely found in the overflow-textframe which ist highlighted as before.
INDS: the anchored textframe is completely missing and its content too!
The (highlighted) overflow-textframe is present with the overflow-text.
The visuability of the overflow-textframes that could be managed by the plugin before is no longer managed by the plugin after opening the inx or placing the inds.
I see, so it is not possible to (re)create the situation via INX.
Sounds reasonable as INX and scripting use the same foundation. Have you filed a bug report at Vjoon? At least with their plugin present it should be possible to rebuild the document, on that way you'd probably also gain scripting support for their feature.