On Mon, 19 Dec 2005 16:53:43 -0700, "Linda G. Gallagher" <[EMAIL PROTECTED]> wrote:
>This is what I call "phantom unresolved cross references," a phenomenon that >I believe started with version 6. I've been able to get rid of these >phantoms by opening the file that is reported as having one or more >unresolved xrefs, saving the file as .mif, opening the .mif file, and saving >it back as .fm (overwriting the old file). We've made that process a *lot* easier with the latest Mif2Go upgrade, 44. We added an item to the File menu, "Wash via MIF", which does just what you want... without disturbing any other MIF file you might have present. It will also "wash" a whole book in one shot, including the .book file itself. And it's really fast, a few seconds tops for most files. It works fine from the demo version of Mif2Go, and we approve of commercial use of this feature with the demo, so it costs nothing to add it to your toolkit. Download and install the (unlimited) demo from: http://www.omsys.com/dcl/download.htm We're going to add more free goodies like this (and runfm.exe) regularly. It's not just for the season. ;-) >In some circumstances, which I've admittedly not delved into deeply, this >happen regularly. I think that conditions have something to do with it. IIRC, when Frame checks cross-references, it checks them all, including those in hidden conditional text. But if the xref source is hidden, it reports the xref as unresolved. It's best to use Show All when checking (or rechecking) xrefs. -- Jeremy H. Griffith, at Omni Systems Inc. <[EMAIL PROTECTED]> http://www.omsys.com/ _______________________________________________ You are currently subscribed to Framers as [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
