False or incomplete error message

[GoogleCodeExporter]

I got this error when closing jBrout, but I couldn't find any jbrout.log,
in the install folder or elsewhere...

Original issue reported on code.google.com by davito...@gmail.com on 10 Jan 2009 at 9:25

Attachments:

• 2009-01-10_222244.png

[GoogleCodeExporter]

windows version, no ?

Original comment by manat...@gmail.com on 10 Jan 2009 at 11:52

[GoogleCodeExporter]

This error message comes from the windows launch wrapper exe which assumes tat 
if
there is a non-zero error level there should be some output in the console log 
file.  

I will have to have a look at changing the way this is handled in the wrapper.  

Was the close of jBrout due to an error ?

Original comment by r...@wallace.gen.nz on 11 Jan 2009 at 10:44

• Changed state: Accepted
• Added labels: OpSys-Windows, Usability

[GoogleCodeExporter]

@manatlan:

Oops. Windows XP SP3, jBrout 0.3.145, manually patched to svn revision 153

@rob:

I dont know. I went away to do something else and when I came back 2 hours 
later the
dialog was there. I don't remember if I had asked jBrout to close before 
leaving or not.

Original comment by davito...@gmail.com on 11 Jan 2009 at 11:07

[GoogleCodeExporter]

... so I just tried to do some tests th check, but now when I load jBrout, I 
have a
similar dialog error code 1. This time the log file is there. It says that the 
lock
file is already present. Checking... no obvious instance of jBrout in the task
manager, so I remove the lock file and I reload. Ok. I resume testing, I'll try 
to
re-trigger the error dialog

Original comment by davito...@gmail.com on 11 Jan 2009 at 11:12

[GoogleCodeExporter]

Sorry, I can't trigger the error dialog again. I tried doing what I did 
yesterday:
moving pictures around and asking jBrout to refresh in order to sort out which 
were
"bad", but I can't get it again. I am convinced that when I left my computer, I
hadn't asked jBrout to do anything. So either it was just waiting or I had 
asked him
to close.

Original comment by davito...@gmail.com on 11 Jan 2009 at 11:49

[GoogleCodeExporter]

@rob:

if it isn't to much work and if it is possible, could the wrapper simply 
display the
contents of the console log file if there is an error? This would avoid sending 
users
exploring folders which are supposed to be hidden.

Original comment by davito...@gmail.com on 11 Jan 2009 at 1:35

[GoogleCodeExporter]

I was either thinking of adding an open log button to the error dailog or 
displaying
the contents of the log file in the error dialog.   

Original comment by r...@wallace.gen.nz on 11 Jan 2009 at 5:32

[GoogleCodeExporter]

I was thinking the same :-) The direct display is better IMO provided we are
reasonably sure the log will fit in a dialog. 

BTW, could you use a control which allows copying? Users could just copy-paste 
the
contents instead of using a screen capture.

Original comment by davito...@gmail.com on 11 Jan 2009 at 6:07

[GoogleCodeExporter]

Original comment by r...@wallace.gen.nz on 13 Jan 2009 at 8:40

• Changed state: Started

[GoogleCodeExporter]

This is fixed in r161.  
The launcher now gives the option of displaying the error log (in Notepad) or 
tells
you there is no log if it does not exist.  

Note: a copy of the new launcher is attached for convenience to save 
downloading the
new installer  which will be up shortly.  

Original comment by r...@wallace.gen.nz on 13 Jan 2009 at 8:52

• Changed state: Fixed

Attachments:

• jBrout.exe

[GoogleCodeExporter]

Nice! Too bad I can't reproduce the bug anymore!

Original comment by davito...@gmail.com on 13 Jan 2009 at 9:04