By registering with us, you'll be able to discuss, share and private message with other members of our community.
SignUp Now!I may not fully understand, but some instance of TCC executes PIPEVIEW. Doesn't that instance of TCC know the filename and V's PID?You're assuming that TCC is the parent pipe process. That is not necessarily the case.
view clip:
or view http://www.jpsoft.com/
, V would show the original source of the text -- not the filename of a temp file, which the user probably doesn't care about.How would V know it's a temp file?It seems to me that deleting a temp file on exit should be V's responsibility, not TCC's. V.EXE ought to have an option meaning "this is a temp file; delete it when you exit." Idea for the next version?
A new option, which TCC could pass to indicate this situation.How would V know it's a temp file?
I don't think Rex has anything to say about how V works. Does V already have such an option?A new option, which TCC could pass to indicate this situation.
No, he'd have to cooperate with Mr. Prineas. I assume that the two are already communicating. In fact, I seem to remember Mr. Prineas being on this forum for a while, though that was some years back.I don't think Rex has anything to say about how V works.
I get it now.No, he'd have to cooperate with Mr. Prineas. I assume that the two are already communicating. In fact, I seem to remember Mr. Prineas being on this forum for a while, though that was some years back.
It should be the responsibility of the program creating the temp file to delete it.deleting a temp file on exit should be V's responsibility, not TCC's
Hmmm! I can think of not-too-costly ways to get around that. When V is started, start a clean-up thread, passing it a pointer to a struct containing V's PID and the file name. The thread would wait for the V process, delete the file, and terminate.
It should be the responsibility of the program creating the temp file to delete it.
That'd be like the city coming out to fix the water meter at your house, digging a huge hole so they can get at the surrounding pipe and then leaving saying... "It was just a temp hole, you fill it."
I think that depends on whether the file may be opened again. The docs say that further attempts to open it will fail if DeleteFile has marked it for deletion.If there is some way to know when V has opened a handle to the file, then AnrDaemon's approach would work too.
That's exactly the intent.The docs say that further attempts to open it will fail if DeleteFile has marked it for deletion.