From: Gerald W. <wol...@gm...> - 2016-11-30 17:20:50
|
The fact that the monitorLog.txt file can be written to two places is news to me. Here is an new replay of the my sequence of logging on my computer. I am running JMRI 4.5.3 under Windows 10 on a ASUS Gamer laptop. In JMRI's Monitor LocoNet, I have both "Show raw data" and "Show timestamps" are checked as well as "Auto scroll" being checked. I started by going to both the program directory and the profile directory (C:\Users\wolfsong\JMRI\My_JMRI_Railroad) and deleting all copies of *.log and .txt files except install.log in program directory (note: did not find any other .log files there). I then went to Monitor LocoNet and did the following steps: 1. Pressed "Choose log lile" 2. Observed that the file name field is filled with "monitorLog.txt" 3. Observed that Save In: was set to "My_JMRI_Railroad". 4. Pressed "Save" to leave the dialog box. 5. Pressed "Clear screen" button. 6. Pressed "Start logging" 7. Rotated throttle on Zephyr back and forth several times. 8. Pressed "Stop logging" 9. Pressed "Freeze screen". Now went back into User Files location and refreshed that screen and saw that a new monitorLog.txt file was there and opened it in Notepad++. The content of the file and the Monitor LocoNet windows matched. Closed the text file and did the following steps: 1. Unfroze the Monitor LocoNet screen. 2. Pressed "Clear screen". 3. Pressed "Start logging". 4. Observed no error message in JMRI System Console. 5. Rotated throttle of Zephyr back and forth several times. 6. Pressed "Freeze screen" 7. Pressed "Stop Logging" 8. Observed still no error message in JMRI System Console. Now went back into User Files location and refreshed that screen and saw that there was still only one monitorLog.txt file in that directory. Opened it in Notepad++ and observed that it matched with the new data collected. Closed the text file and did the following steps: 1.Unfroze the Monitor LocoNet screen. 2. Pressed "Clear screen" 3. Pressed "Choose log file" 4. Pressed "Cancel" to exit dialog box 5. Pressed "Start Logging" 6. Rotated throttle several times. 7. Pressed "Stop Logging" 8. Pressed "Freeze screen" 9. Observed still no error messages in JMRI System Console. Now opened refreshed User Files directory window and opened only monitorLog.txt file. File again matched with Monitor LocoNet screen. Closed Panel Pro completely and then reopened. Then did the following: 1. Opened Monitor LocoNet (all checkboxes same as before) 2. Pressed "Choose log file" (see content is same as before) 3. Pressed "Cancel" to exit. 4. Pressed "Clear screen". 5. Pressed "Start logging" 6. Observed "2016-11-30 12:08:13,091 jmrix.AbstractMonPane ERROR - exception java.io.FileNotFoundException: monitorLog.txt (Access is denied) [AWT-EventQueue-0]" message in JRMI System Console window. 7. Rotated throttle several times. 8. Pressed "Stop Logging" 9. Pressed "Freeze screen" 10. Opened monitorLog.txt in Notepad++ 11. Observed data and timestamps were from the previous capture. Conclusion: When JMRI is launched, there is no default filename string prior to the "Choose log file" use and save. (didn't test to see what it would do on "Cancel" in this case.) The reason if showed up in my case was that I had to get out of Panel Pro to correct some script code which only gets loaded at JMRI launch and as a result my next logging of activity did not know the name of the last logging file I used nor did it have a default string without my having to go back into "Choose log file" and setting it again. I would suggest there be a default string or a warning that a name is not present if the "Start logging" button is pressed or remember the last name used for JRMI launch to launch. =gerry= On Tue, Nov 29, 2016 at 9:31 PM, B. Milhaupt <dcc...@sb...> wrote: > Gerry and all, > > > > I think Walt is onto something here. I've done some experimentation, > with three basic scenarios (not all the possible scenarios, but the ones of > interest in the discussion so far, I think): > > > > a) User does not "Choose log file". Instead he activates "Start logging". > > b) User selects "Choose log file", and then "Cancel", without changing > directory and without modifying the displayed file name. > > c) User selects "Choose log file" and then "Ok", without changing > directory and without modifying the displayed file name. > > > > Cases a) and b) result in a log file "monitorLog.txt" in the program > directory (if user privileges permit!), while case c) results in a log file > "monitorLog.txt" in the profile directory. > > > > When I try cases a) and b) on my Win7 machine, I get an "access denied" > exception when running an "installed executable", and when I run within my > development IDE, I get a monitorLog.txt file in the development (build) > directory. > > > > It seems that the behavior among these three cases should be normalized - > monitor log files should default to the "profile" directory, and not to the > program directory. Especially since the program directory may not be > accessible by the typical users of many modern operating systems. > > > > Regards, > Bob M. > > > > *From:* Walter Thompson [mailto:wal...@gm...] > *Sent:* Tuesday, November 29, 2016 11:01 AM > *To:* Discussions between JMRI developers <jmri-developers@lists. > sourceforge.net> > *Subject:* Re: [Jmri-developers] add overwrite dialog to loconet monitor > logging > > > > gerry: > > Do a search on your computer for the log file name. I think you will find > a couple of them. > > Walt > > > > On Tue, Nov 29, 2016 at 8:52 AM, Gerald Wolfson <wol...@gm...> > wrote: > > I don't think it is a lock issue. I am opening the log file with Notepad++ > > =gerry= > > > > On Mon, Nov 28, 2016 at 10:58 PM, Ken Cameron <kca...@tw...> > wrote: > > Walt, > > > > Had you used OpenOffice to read the log file?? If so, I’m thinking some > sort of file locking hangup and it wasn’t showing anywhere. Otherwise some > sort of buffer or memory issue with Java. Just guesses here. > > > > -Ken Cameron, Member JMRI Dev Team > > www.jmri.org > > www.fingerlakeslivesteamers.org > > www.cnymod.com > > www.syracusemodelrr.org > > > > > > > > ---------- Forwarded message ---------- > From: Walter Thompson <wal...@gm...> > To: Discussions between JMRI developers <jmri-developers@lists. > sourceforge.net> > > Cc: > Date: Mon, 28 Nov 2016 19:59:53 -0500 > Subject: Re: [Jmri-developers] add overwrite dialog to loconet monitor > logging > > Bob M. > > I tried playing with this. First found that if Time Stamps was enabled it > would add to the saved log. Then tried without time stamps and it failed. > > > > Then things really went down hill. Running Win 10 and OpenOffiice, for > some reason OpenOffice would no longer work. Finally found that deleting > the Log file recovered so OpenOfiice would start. > > > > No clue as to what it all means. > > > > Walt > > > > On Mon, Nov 28, 2016 at 4:13 PM, B. Milhaupt < > dcc...@sb...> wrote: > > Gerry, > > > > I had difficulty reproducing the problem you report - amost everything I > tried worked the way I would want - i.e. overwriting the pre-existing > data. But I was able to trigger it, I think. > > > > The following sequence seemed to do the trick: > > a) start JMRI. Open LocoNet monitor. > > b) select "Choose Log File" and enter a filename. > > c) select "Start logging". > > d) generate some LocoNet traffic. > > e) "Stop logging". > > f) quit JMRI. > > g) verify that logged info is in the specified file. > > h) start JMRI. Open LocoNet monitor. > > j) select "Choose Log File". Select the same filename ase used in step b) > above. > > k) select "Start logging". > > l) generate some different LocoNet traffic. > > m) "Stop logging". > > n) quit JMRI. > > p) check the specified file - does it contain old or new info? > > > > When I tried this sequence, in step p), I found logged info from traffic > in step d), not the traffic from step l). It seems that qutting JMRI was > necessary to cause the type of failure you reported. > > > > Is this consistent with what you've seen? > > > > Regards, > > Bob M. > > > > > > *From:* Gerald Wolfson [mailto:wol...@gm...] > *Sent:* Thursday, November 24, 2016 10:55 AM > *To:* Discussions between JMRI developers <jmri-developers@lists. > sourceforge.net> > *Subject:* [Jmri-developers] add overwrite dialog to loconet monitor > logging > > > > Hi, > > I painfully discovered that when using the Start Logging button on the > LocoNet Monitor, if a file already exists by the current filename selected, > absolutely nothing is captured and the user is never told the process was > ignored. I had to do several captures before I realized that the old file > was not getting replaced. > > > > If I changed the name to a non-existing file, then it worked. But the next > time it would fail again until I gave it a new filename or went into the > folder and deleted the current file by that name. > > > > I would suggest when you press the Start Logging button and a file by the > currently selected name exists that a dialogbox appear which lets you > overwrite the old file or abhort and select a new name. > > > > This will help new users (and old) since it is not an intuitive as it > stands. > > =gerry= > > > ------------------------------------------------------------ > ------------------ > > _______________________________________________ > Jmri-developers mailing list > Jmr...@li... > https://lists.sourceforge.net/lists/listinfo/jmri-developers > > > > > ------------------------------------------------------------ > ------------------ > > _______________________________________________ > Jmri-developers mailing list > Jmr...@li... > https://lists.sourceforge.net/lists/listinfo/jmri-developers > > > > > ------------------------------------------------------------ > ------------------ > > _______________________________________________ > Jmri-developers mailing list > Jmr...@li... > https://lists.sourceforge.net/lists/listinfo/jmri-developers > > > > ------------------------------------------------------------ > ------------------ > > _______________________________________________ > Jmri-developers mailing list > Jmr...@li... > https://lists.sourceforge.net/lists/listinfo/jmri-developers > > |