Hi Gary, Here is an idea for solving this with a script. Each text inset has a "Unique" property, which acts as a serial number for the inset. This number remains constant, even after the inset is updated. You could follow a workflow similar to this.
1) Import and correctly conditionalize your insets. 2) Run a script that would loop through the insets and pick up its Unique value and the current condtion applied. This information would be stored in some kind of "database." 3) After insets are updated, another script would be run that would "lookup" each text inset's Unique value in the database and retrieve the appropriate condition for that inset. The script would apply the proper condition to each text inset. Of course, a script like this could be run on a single document, book, or an entire folder (and subfolders) of documents. It could be further automated so that the first script could be run automatically whenever the document is closed, and the second script could be run automatically when the script is opened (after the insets are updated). As usual, with FrameScript the sky is the limit. Rick Quatro Carmen Publishing 585-659-8267 www.frameexpert.com ----- Original Message ----- From: "Duncan, Gary" <gary.dun...@kronos.com> To: <framers at lists.frameusers.com> Sent: Thursday, April 24, 2008 8:20 AM Subject: Conditional text insets > Hi everyone, > > > > We are trying to use text insets that get called into the chapter and > then are conditionalized from within the container file. For example, if > we want the content of an inset to appear only in Help, we give it a > HelpOnly condition from within the container file. We do not want to > conditionalize the text inset content itself because the condition may > not be appropriate in other places we use the inset. > > > > This works fine until we revise the inset and it gets called back into > the container file. The condition is lost. At first, it seemed like a > bug. But after thinking about it, it makes sense that reimporting the > text inset replaces everything associated with the previous version. The > buggy thing is that Frame still indicates that the inset is conditional > (in the lower left corner of the screen where the paragraph/flow info > shows). The conditional dialog indicates that the inset is conditional, > but does not indicate which condition. In the end, however, the > information seems bogus because if you click on something else, then > click back on the inset, the info is carried over from the previous text > you clicked on. > > > > If the conditional info was truly held in Frame, I was hoping that a > solution could be a script that scans for insets with associated > conditions and update and apply the condition. Now, I am not so hopeful. > > > > Has anyone run into this and solved the problem? > > > > Thank you... > > > > Gary > > _______________________________________________ > > > You are currently subscribed to Framers as frameexpert at truevine.net. > > Send list messages to framers at lists.frameusers.com. > > To unsubscribe send a blank email to > framers-unsubscribe at lists.frameusers.com > or visit > http://lists.frameusers.com/mailman/options/framers/frameexpert%40truevine.net > > Send administrative questions to listadmin at frameusers.com. Visit > http://www.frameusers.com/ for more resources and info. >