The
NOSHOW
terms of theTEXT
command suppresses result to the major Fox screen but the output still displays up in a journal file fixed withCollection Alternative
. Can the text output be held out of the text file somehow? Example:Ideas, Concepts and Implementations with Visual FoxPro and other (OOP) Languages. VFP's Editor Code RTF2HTML (Part 2). Now, let us drop the closing bracket at the end of our RTF text. As you can see in figure #5 this is too much for our RTF control - finally it fails silently. Figure #5: Too much of a good thing. Text property. ORange.Text = 'This is a new sentence.' You can also add text to whatever's already there. Simple text manipulation does the trick. ORange.Text = oRange.Text + 'Add text at the end.' Or oRange.Text = 'Add text at the beginning ' + oRange.Text Another possibility is to read text into VFP, manipulate it in some way and write back.
Issuing
Collection Gaming console OFF
has no effect.History: I desire to catch the text that gets result to the Fox screen but the code that produces the result contains some
DarthGizkaDarthGizkaTEXT NOSHOW. ENDTEXT
obstructions for initialising multi-dimensional hunt arrays in worker items. That text ends up in the file as nicely and can make it essentially worthless, with a noise to signal proportion of about 1000 to 1. I don't wish to move out and break the harmless worker code by encircling theText message
pads withCollection ALTE
fiddling, therefore this issue.2,66311 silver logo1212 metallic badges3030 bronze badges
2 Solutions
Rather of text. endtext you could make use of Set Textmerge. web browser:
Cetin BasozCetin Basoz11.3k11 gold logo1616 silver badges2929 bronze badges
The objective was two fold. The main objective has been to catch result to a document for simple perusal - output that had been the result of some leftover prototype/research code that could become useful in additional prototyping/study. Instance:
Hacking kLOCs of stuff like that to make use of a various output method would long been more work than it was worth. On the some other hand, the interspersal with TEXT command output at a signal-to-noise percentage of 1 to 1000 produced the captured output efficiently worthless.
The 2nd objective had beennotto munge - and potentially break - the harmless library program code that has been making use of
Text message NOSHO. ENDT
internally. So it was the consumer program code that experienced to give way. In order to keep interruption/noise to a least a built a easy SET-ALTE-OFF course that can become used in strategic places to cover TEXTy collection phone calls like therefore:In fact it's all of the surrounding code that results interesting details, and just a small handful of TEXTy library phone calls.
Of all the alternatives considered, this adds the least amount of sound to the source code and it is usually secure in the face of exceptions hurtling about, without needing an explicit
FINALLY
body and hence working actually under Foxen that predate VFP8.Normally, the class is basic and straightforward:
Job completed with a least of fuss.
The actions of
DarthGizkaDarthGizkaTEXT NOSHOW. ENDTEXT
vs.Place ALTERNATE
records is still mighty odd, though.2,66311 gold badge1212 metallic badges3030 bronze badges