Re: NB...BB blocks that did break and shouldn't

[TBaehr@xxxxxxxx]

Re programs that execute within programs: This could be added to the Print
command in a U2 file; much experimentation and debugging would be needed.
 One experiment you could try is to put a program in a text file, surrounded
by the IV (invisible) command. The program would have to appear a the end,
or it would have to be sure that all its exit points ended with EX. The most
obvious use would be a program that operated solely within the document, but
there's no reason it couldn't call other files, do merges, etc. I've never
had occasion to try this, but it seems like it ought to work if the program
interpreter can "see" through the IV command. Then you just issue RUN
[filename] from the command line, where [filename] is the text file
containing the program. The programs themselves, if they could be generic,
could be stored as TPL template files, and you could even rejigger the menus
routines around the New dialog to execute anything inside a TPL file that
they find. Shades of some of the stuff in Word, running macros when a file
is opened. It's conceivable you could even have embedded commands that would
run out-of-file routines, but I haven't figured that one out yet.

The Link routines for Import and Manage Links do something similar. When you
update a link thru Manage Links, XyWrite executes some out-of-file routines,
including file format filters. I doubt the link stuff could be modified to
run routines other than the filters, but it's an intriguing concept.

Be aware that these are ideas only and that I haven't tried any of them.

Good luck

Tim Baehr
tbaehr@xxxxxxxx (which seems to be working better nowadays)