As long as your text insets and container files have exactly the same conditional text options, when you pull in a text inset into a container file, this text inset inherits the conditional text setting of the container file. For example, let's say in a container file, you have Condition and Condition B, and you elect to show Condition A, but not Condition B. If you pull in a text inset that is unconditional, then it will always show. If you pull in a text inset that also has the conditions and you have elected show Condition A in the text inset, then when you pull in the text inset, it will show in the container file. If you have elected to show Condition B in the inset, then when you pull in the text inset, it will NOT show up in the container file, because the container file is set to show condition A. To get the text inset to show in the container file, you need to set the container file to show Condition B.
I do this set up all the time with hundreds and hundreds of text insets and many container files without any scripts. Let's say that I know that a text inset is about 90% the same when used between two container files, but 5% is needed only for Container file A and the other 5% is needed for only Container file B. I make sure that both container files have the conditions ContainerA and ContainerB. In the text inset, which must have the same conditions, I apply the condition of ContainerA to the text that I only want to show up in the Container A file. I apply the condition of ContainerB to the text that I only want to show up in the Container B file. Then, I make sure that in the Container A file, that the ContainerA condition is set to show and that the ContainerB condition is set to hide, then when I pull in the text inset, only the text marked for Container A show. (and obviously, just flip this scenario for Container B). The trick is to conditionalize your inset (all or part) BEFORE you pull it into the container file and make sure that container file and text inset have the EXACT same conditional text options. The text inset then inherits the settings of the container file. HTH, TVB -----Original Message----- From: framers-bounces at lists.frameusers.com [mailto:framers-boun...@lists.frameusers.com] On Behalf Of Stephen O'Brien Sent: Friday, April 25, 2008 1:12 PM To: Duncan, Gary; framers at lists.frameusers.com Subject: Re: Conditional text insets Not sure I understand the problem. But I am interested because I use text insets (several hundred) and conditional text formats (twenty). Let's say that Doc1 has a text inset Doc2 which has three conditional formats A, B, and C. If in Doc1 I want to see only the content of Doc2 that is flagged with condition C, I set show condition C in Doc1 and that's that. No problem. The only time I had a problem with this is when I had the following case: Doc1 has a text inset Doc2 with a text inset Doc 3 (with conditional formats called A, B, and C). I set show condition C in Doc1 and it didn't work! The problem I believe was that the condition was not defined the same way in Doc2 so the specification didn't make it to Doc3. I deleted the condition in Doc2 and then the correct condition definition (created in Doc3) was imported into Doc2 and then Doc1. I wonder if this is clear..helps. I don't understand how/why a script would be useful here. I probably don't quite understand the problem. Good luck. At 08:20 AM 24/04/2008, Duncan, Gary wrote: >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 sobrien at innovmetric.com. > >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/sobrien%40innovmetr >ic.com > >Send administrative questions to listadmin at frameusers.com. Visit >http://www.frameusers.com/ for more resources and info. Stephen O'Brien Technical Writer / R?dacteur technique InnovMetric Software Inc. / InnovMetric Logiciels inc. 2014, Cyrille-Duquet, suite 310 Qu?bec (Qu?bec) Canada G1N 4N6 Tel.: (418) 688-2061 Fax: (418) 688-3001 E-mail: sobrien at innovmetric.com www.innovmetric.com PolyWorks, the Universal 3D Metrology Software Platform for Manufacturing (TM) Don't miss the upcoming International PolyWorks User Meeting on May 29-30, 2008, in Montreal, Canada! <http://www.innovmetric.com/Manufacturing/ipum2008.aspx>Register Today! Ne manquez pas le prochain Congr?s international des utilisateurs de PolyWorks les 29 et 30 mai 2008, ? Montr?al, Canada! <http://www.innovmetric.com/Manufacturing/ipum2008.aspx?lang=fr>Inscrivez-vous d?s aujourd'hui! _______________________________________________ You are currently subscribed to Framers as tammy.vanboening at healthlanguage.com. 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/tammy.vanboening%40healthlanguage.com Send administrative questions to listadmin at frameusers.com. Visit http://www.frameusers.com/ for more resources and info. ---- NOTICE BY HEALTH LANGUAGE, INC. This message, as well as any attached document, contains information from Health Language, Inc. that is confidential. The information is intended only for the use of the addressee named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of this message or its attachments is strictly prohibited, and may be unlawful. If you have received this message in error, please delete all electronic copies of this message and its attachments, if any, destroy any hard copies you may have created, without disclosing the contents, and notify the sender immediately. Unless expressly stated otherwise, nothing contained in this message should be construed as a digital or electronic signature, nor is it intended to reflect an intention to make an agreement by electronic means.