[Date Prev][Date Next] [Thread Prev][Thread Next]
[Date Index] [Thread Index] [New search]

Re: Distinguishing Text Insets

     
     
     
     My condition tags don't do a disappearing act like Lynne mentioned.
     
     This works (with one condition tag per inset):
     Import the inset by reference with automatic updating. 
     Open the inset and apply a condition tag to the whole flow. Close it, 
     then single-click the inset in the container doc and apply the 
     identical condition tag to the selection. 
     This is robust and will survive updates!
     
     


______________________________ Reply Separator _________________________________
Subject: Re: Distinguishing Text Insets
Author:  jeremy (jeremy@omsys.com) at internet
Date:    23/10/01 10:30


On Mon, 22 Oct 2001 22:06:28 -0700, "Lynne A. Price" 
<lprice@txstruct.com> wrote:
     
>At 03:25 AM 10/23/01 GMT, Jeremy wrote: 
>>Lynne wrote:
>>>  Warning: if you update text insets, the condition tag 
>>>is discarded so you need to reapply.
>>
>>Didn't know that.  Thanks!
>
>  You are quite welcome. I just encountered this situation fairly 
>recently. It sort of makes sense--updating a text inset produces the 
>same result as deleting and reinserting the text inset and, of course, 
>that approach would not preserve the condition tag.
     
Yes, it makes sense, and it is not good news.  In fact, 
it pretty much prevents the use of conditions within a 
container document to select among components that are 
being maintained as insets.  This forces one container 
doc for every variation in usage, which can require lots 
of containers...
     
Unless, that is, some clever FDK hacker felt like making 
a utility that recorded and restored condition settings
around inset updates.  A bit like the TOC-line-break tool, 
perhaps.  Or maybe just a smarter update replacement... 
that *did* preserve conditions.
     
-- Jeremy H. Griffith, at Omni Systems Inc.
  (jeremy@omsys.com)  http://www.omsys.com/
     
** To unsubscribe, send a message to majordomo@omsys.com ** 
** with "unsubscribe framers" (no quotes) in the body.   **


** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **