Mail Archives: djgpp/1997/02/14/13:57:50
On Thu, 13 Feb 1997, Robert Hoehne wrote:
> Peter Berdeklis wrote:
> >
> > very useful, I think it's checking the _access_ time rather than the
> > _modification_ time. Rhide asks to reload any open file after a compile,
> > or even if I drop to DOS and do a less on the file.
> I know that fact and it is fixed now. But are you sure, that RHIDE asks
> ever for any opened file?? When I remember correct, the bug was in the
> fact, that I gave the opened file the last modification time from
> a call to ftime() which is second accurate, but the time, which
> is stored on disk for a file is 2second accurate, so there was
> sometimes a difference of 1 second only because of rounding.
Hi Robert.
Open a project and immediately go to DOS. Immediately return from DOS,
or do something while you're in DOS if you like. Rhide will ask if you
want to reload _every_ open file.
Open a project and don't change any of the open files. Hit F9 to make.
It will re-compile all of the open files, even though you haven't modified
them, and after ask if you want to reload them.
If you've changed and saved one of the open files before making the
project, then Rhide wont ask you to reload the file (of course it does
compile the file). The same is true if you save before dropping to DOS.
All of this behaviour stops after the first time you're asked to reload
the files or you have saved the file. If you open a new file in the
middle of a session and do any of the above you get that behaviour for that
file only.
Obviously you're not initializing some data structure for the file.
Sorry I suggested before that it was happening always. At the time I
noticed it I was exiting and restarting Rhide all the time, and didn't
notice the connection to newly opened files.
Hope this helps.
---------------
Peter Berdeklis
Dept. of Physics, Univ. of Toronto
- Raw text -