Melchior FRANZ wrote :
>> line 388, file sample_openal.cxx, there is :
>>
> [...]
>
>> This throw needs a try {} catch {} somewhere. I will commit a fix soon.
>>
>
> Would be useful. But it is not the reason why fgfs doesn't show
> the exception text, as I explained above.
>
It's a bit frustrating to exit because the sound is not working, or not
setup correctly. That draws a lot of frustrations, and angry complains
we see on the forums could be attributed to that.
I commited a patch where exceptions are caught nearer of their throw, so
we can use a degraded, silent, but working, code path.
An alert should be displayed, because the try/catch is at the right side
of GLUT.
Isao, update CVS, and tell us if FG is still aborting for you. If yes,
send a new backtrace.
-Fred
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
