error banner popped up: Oh oh ... Something went wrong ...

[JD]

On 08/25/2012 06:41 PM, Joe Zeff wrote:
> On 08/25/2012 04:28 PM, JD wrote:
>> The way the apps are stacked so deeply upon lib after lib, by the time
>> the failure
>> is returned to the calling app, the app has no ide what happened. The
>> high library
>> stack is very likely to blame.
>
> So?  Each lib that detects an error should log it instead of just 
> returning with an error status-code.  Yes, I know that this sometimes 
> means eight or ten lines in the log for one issue, but something like 
> that makes it easy to spot.  As is, there doesn't seem to be any 
> reliable way to track things back to the root cause.
Yes, that is right. But heck ... much of this freeware was coded without 
the foresight of such deeply stacked calls.
So, I would say I excuse them just because it is hard to foresee all the 
possible side effects when so many different
libraries call upon each other to accomplish one func call by the top 
level app. Logging errors is a good thing, but
it has to be done so that they are all in one log file and the user can 
trace it back from the deepest call all the way
to the app and it's pid (which may be dead and gone by then).

All in all, I find it totally amazing that it all works as well as it 
does, instead of falling to pieces :)

Cheers,

JD