[softwarelist] OvPro and RTF
- From: Dave Symes <dave@xxxxxxxxxxxxx>
- To: <davidpilling@xxxxxxxxxxxxx>
- Date: Sun, 06 Mar 2011 06:14:00 +0000 (GMT)
In article <Xi4FRUFpPrcNFw$l@xxxxxxxxxxxxxxxxxxx>,
David Pilling <flist@xxxxxxxxxxxxxxxxxxx> wrote:
> Hi,
> In message <51af62f08ddave@xxxxxxxxxxxxx>, Dave Symes
> <dave@xxxxxxxxxxxxx> writes
> >If !MakeRTF is run, then OvPro is only run later it doesn't work.
> Maybe another copy of MakeRTF inside OP, people like to put things in
> the Autorun folder (not my idea).
Sorry Chief me thicko injun. ;-)
Do you mean I should put a copy of MakeRTF inside the Autorun folder?
Or do you mean I should look in there for another copy of MakeRTF that
possibly shouldn't be there?
Anyway... There obviously wasn't a copy in there (I'm not that thick) so
just in the spirit of experimentation, I put a copy in there and Ran OvPro.
Didn't make any difference at all.
OvPro "Save as" RTF output a file that was sans the required changes.
I double clicked MakeRTF, did a "Save as" and the output file did contain
the changes.
Normally I have !MakeRTF in the Boot.Choices "Lookat" and "Run" but that
doesn't make any difference either, as it will only work if MakeRTF is Run
after OvPro.
It appears to this thicko, that OvPro when it is Run, is not seeing that
MakeRTF is already active.
So why might that be?
Probably MakeRTF not registering itself correctly (Oh we don't have a
Registry on this side do we...) So how does it work?
> Well done to Chris for getting this right, I misunderstood. The "code"
> (scary) in fluff is quite simple, a list of function calls with text to
> search and text to replace. But getting MakeRTF right is a much better
> solution.
And Indeed thanks from Her to Martin for the initial posting.
Dave
--
Dave Triffid
To unsubscribe or subscribe goto: //www.freelists.org/list/davidpilling
Other related posts:
