Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.comp.os.windows-xp    |    Actually wasn't too bad for a M$-OS    |    17,273 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 16,764 of 17,273    |
|    VanguardLH to R.Wieser    |
|    Re: Reloading a changed a wordpad docume    |
|    25 Mar 24 15:22:21    |
      XPost: alt.windows7.general       From: V@nguard.LH              "R.Wieser" wrote:              > I've got a program which generates a wordpad document, which I than       > open by double-clicking it.              No such thing as a Wordpad filetype. Do you mean an RTF (Rich Text       Format) file, so you can have formatting since text doesn't? Is there       any formatting in the file (i.e., is it just a text file you could open       in Notepad)?              Other programs can open an RTF file, like Word, LibreOffice, and even       Wordpad. RTF is not solely a "Wordpad document".              > The problem is that when the document is open and I re-generate the       > document and double-click it I still see the old contents. To see       > the new contents I have to close the old, still-open document first.              You can't get your "program" to timestamp its output file, like       file_yymmddhhss (year, month, day, hour, seconds)? Then Wordpad would       have a different target to load instead of failing to open a locked       file. You have a file handle with write state since you already have it       opened for write in Wordpad. Wordpad is an editor, not a viewer.              The "program" should not be stepping atop an existing file (that it       created before) without a prompt asking for you to grant it to       overwrite. At the prompt, if properly coded, the program should allow       you to specify a different filename. What happens when the program       attempts to write to the same file, but it is locked (another process       has write access on the file, like an editor)? A write-locked file for       one process can still be read by another process, but other-process       writes should be blocked to prevent yanking away a document on which you       are currently working.              > Question: Is there a way to override this behaviour using a       > command-line argument ? Even just having two document windows open       > would be an improvement.              The only command-line argument I've heard of for wordpad.exe,       notepad.exe, and write.exe (other than a filespec) is /p which is       somehow used for printing.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca