Just toggle the option to dump the log to a specified file.
On Tue, Feb 18, 2014 at 1:54 AM, Matt Lind <[email protected]> wrote: > Softimage does have a preference for logging to a text file, but that text > file is not accessible while Softimage is running. The only way to get > access to the log contents is to exit softimage and wait for the log to be > released. > > > > One problem is the text file is reused between sessions of Softimage. If > you exit the application, then restart, Softimage overwrites the file with > the output from the new session - again remaining not accessible until > Softimage exits. If the artist forgets to copy the log between sessions of > Softimage (almost a given), the data is lost. > > > > A 2nd problem with the text file preference is it does not take effect > until the next session. Originally I tried driving the value of that > parameter via the siOnStartup event, but the specified filename wouldn't > become the official log until the current session was terminated and the > application restarted. If we could get a live switch, that would be useful > for this purpose. > > > > What I need is a quick dump of the script log contents so it can be > attached to a bug report for our custom tools. The bugs aren't necessarily > for crashes, but to help troubleshoot when tools don't do what is expected > and we need the log to trace what the user has done leading up the > problem. It's handy that Softimage provides the current line number in the > log, which we can record as a start point when the tool is launched so we > only grab relevant output, but the fact we cannot get all the following > lines is a problem. Some tools generate massive amounts of information in > their debug output, it would be nice to cull some of that down so people > troubleshooting the reported issues aren't overwhelmed with noise. We can > do that by prepending the beginning each line of output with a keyword, > then let the dump tool cull out all lines that do not contain the keyword, > for example. But to do that requires we get access to the log contents > beyond the current line. > > > > > > > > Matt > > > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Siew Yi Liang > *Sent:* Monday, February 17, 2014 8:29 PM > *To:* [email protected] > *Subject:* Re: how to obtain full script editor history > > > > Um, maybe I'm misunderstanding, but doesn't the script editor have the > option in prefs to write to a text file? > > Scripting > Log to File > > You could run a simple python script to trim 'n' lines in the document and > write it to a seperate file... > > Yours sincerely, > > > Siew Yi Liang > > On 2/17/2014 8:11 PM, Matt Lind wrote: > > I need to write a simple command to dump the script editor history log (or > 'n' lines at the tail end of the log) to a text file so artists may attach > the file to an issue in our bug tracking system. From what I've seen in > the SDK docs, View.GetAttributeValue() only returns the last line, or the > selected line. I need the entire contents. > > > > Anybody have to deal with this and come up with any backdoor tricks to get > the full script log? > > thanks, > > > > > Matt > > >
