[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: "Lynne A. Price" <lprice@xxxxxxxxxxxx>
Subject: Re: Distinguishing Text Insets
From: jeremy@xxxxxxxxx (Jeremy H. Griffith)
Date: Tue, 23 Oct 2001 03:25:41 GMT
Cc: "Mitchell, Sue" <Sue.Mitchell@xxxxxxxxxx>, "'Framers (framers@xxxxxxxxx)'" <framers@xxxxxxxxx>
In-Reply-To: <3.0.1.32.20011022170030.0092d100@pop.business.earthlink.net>
Organization: Omni Systems, Inc.
References: <FB15E670DA55D51185350008C786514A011C368D@sottexch1.cognos.com> <FB15E670DA55D51185350008C786514A011C368D@sottexch1.cognos.com> <3.0.1.32.20011022170030.0092d100@pop.business.earthlink.net>
Sender: owner-framers@xxxxxxxxx
On Mon, 22 Oct 2001 17:00:30 -0700, "Lynne A. Price" <lprice@txstruct.com> wrote: > Let me just add to Jeremy's suggestion is that you can copy the condition >tag to the clipboard and then do a global find/change of any text inset >by pasting. Very good, Lynne! And here I'd just mentioned you in an off-list post to Sue... ;-) This makes it a *workable* solution. > Warning: if you update text insets, the condition tag is discarded so >you need to reapply. Didn't know that. Thanks! -- 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. **