NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

Unsolicited screenshots More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

How about an MP3 of me describing the problem? (Score:2)

by merlyn (47)
Or an MP4 of a video capture of me handwaving while describing the problem?
--
- Randal L. Schwartz
- Stonehenge
Yes, not so obvious... (Score:1)

by Alias (5735)

Why would people be sending you screenshots exactly?
- Re:Yes, not so obvious... (Score:2)
  
  by jdavidb (1361)
  
  Allegedly to illustrate the problem.
  
  --
  J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
A picture is worth a, er (Score:2)

by rafael (2125)

Reminds me the day we got at perl5-porters a bug report containing a jpeg file, copy of a DOS console displaying a rather trivial perl error (such as "Global symbol requires explicit package name" or so). (Can't find it now.) Nicholas commented privately that this way of reporting bug was crap: the reported could have used, at least, a lossless image compression format!
Unfortunately, this is SOP where I work (Score:1)

by runrig (3385)

If users have a problem with our GUI app, they'll copy the entire screen and send it rather than just describe what the problem is. When there's a SQL error, a box pops up with the current SQL statement. Unfortunately, it's a scrolled box and the statement is usually truncated in the screenshot. I often have to tell them to copy and paste all of the text in that box :-)
- Re:Unfortunately, this is SOP where I work (Score:1)
  
  by Alias (5735)
  
  Sounds like you need a "Report This Problem" button on the SQL dump thing.
so what's the problem...? (Score:2)

by jhi (318)

I used to routinely debug intranet apps (web frontend, db backend) using Windows .BMP snapshots, each sized several dozen megabytes... it made one debug fast unless I wanted my email quota to run out pretty quickly.
- Re:so what's the problem...? (Score:2)
  
  by jdavidb (1361)
  
  File size is often a problem, but the big problem is the often irrelevancy or redundancy of the screenshots.
  
  --
  J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
- Re:so what's the problem...? (Score:2)
  
  by jdavidb (1361)
  
  Oh, and sending it to me when I'm not the one responsible for the problem (because you CC'ed it to everybody and their dog) is also a problem, particularly if it's a really big file.
  
  I have very few apps for which a screenshot would help in debugging.
  
  --
  J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers