Rigel wrote:
Let me know if I should direct this to the developers list instead.
Can I PLEASE get some feedback here? I try to cover worth while issues
and often get few or no responses... :(
Is there any way to make the logging feature of OOo run in a
foreground state so I can see everything as it happens? This way I
when "I" or "Anyone else" send in an error report we can specificaly
say. "I did this, and the at that moment the log file registered
that." In this way, the developers and debug team could have a direct
correlation every step of the way if some users want to be generous
enough to identify the exact moment in time that something happened.
In fact this could be extended even further to run OOo in debug mode
hmm. first, oo.org can be run from commandline, which might provide some
insight into the problem.
then, depending on the problem (but here probably some developer advice
should be needed to find out what data is needed) strace/gdb/valgrind
could be used to get a lots and lots of data :)
or have i misunderstood the problem ?
which could be ALOT simpler for end users, and not that difficult for
developers. It would just involve an "Inser tag here" kind of command
into the logging mechanism where the user simply has a button in the
bottom right of the application and when they hit any critical moment
in the process they can tell the logger to "tag this!" and add a
comment. This would put in a descriptive block right above or below
the command that was either a problem or what the user considered a
key point where OOo went foul handling their data or the API went
tits-up so to speak.
unless oo.org completely stops, there probably would be a lot of
information between the exact moment and "user tag".
I think the latter option would be a better course of action for end
users, but for the geeks and nerds (like me) I KNOW they'll want to
pry into the processes.
Rigel
--
Rich
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
