After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 107519 - on Windows, g_log/g_warning should go to Log Window, not console
on Windows, g_log/g_warning should go to Log Window, not console
Status: RESOLVED FIXED
Product: Pan
Classification: Other
Component: general
0.13.4
Other Linux
: Normal normal
: 0.14.0
Assigned To: Charles Kerr
Pan QA Team
: 107325 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-03-04 04:05 UTC by Charles Kerr
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Charles Kerr 2003-03-04 04:05:30 UTC
It would be better to route g_log() and g_warning() messages
to Pan's Tools|Log Viewer window, at least on Windows:

* writing to the console pops up a console window behind the
  app, which is annoying to Windows users and hard to capture
  output from.
* by writing the output to the Log Viewer, users can save the
  messages in a text file that can be attached to bug reports.

Consider this message from another satisfied Pan customer
on news.software.readers:

> I will try it again when another Beta is issued.  I will also
> be better prepared to capture the screen.  I just happened to
> have failed to install a screen capture utility this go-around,
> so was unable to capture the output of the Console window.
> Capturing screens using "Alt-PrintScrn" only saves HUGE .bmp files.
> I would hate to email large files to you, when it is much simpler
> to install a screen-capture utility.
Comment 2 Charles Kerr 2003-08-12 13:57:06 UTC
*** Bug 107325 has been marked as a duplicate of this bug. ***