Title: | Archive/Backup |
Moderator: | COOKIE::MHUA IG |
Created: | Wed Sep 08 1993 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 479 |
Total number of notes: | 2283 |
Hi, one more for the whishlist for the next ABS GUI. Despite the fact, that the GUI is running fairly stable now, it sometimes bombs out and does not leave the main window to click 'SAVE LOG' to capture, what was written out. What would be needed is either a GUI-supported way to switch logging of window output on/off, or simply a logical name, which - when defined - points to a file, into which all text output gets written as well. This would simplify the tracking of problems, especially, if they are not easy to reproduce. Ewald.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
431.1 | COOKIE::MHUA | Thu Apr 17 1997 14:46 | 9 | ||
The current GUI has a wasy to save a log to a file (under "file" pull down). We'll put this in the newly revised future version functionality wish list. However, depending on the technology we use to produce GUI, this may or may not be possible, I think. Masami | |||||
431.2 | There needs to be a way... | ATZIS1::PIEBER | chaos has many faces | Fri Apr 18 1997 03:09 | 12 |
> The current GUI has a wasy to save a log to a file (under "file" pull > down). That's exactly what does *NOT* work for the issue described in .0 ! > list. However, depending on the technology we use to produce GUI, this > may or may not be possible, I think. I think, regardless to which technolgy is used, there needs to be a way to at least capture the error message, in case the GUI crashes. Ewald. |