bug_report_picture

One picture on a report - the in-game capture, a capture of one of the reporter's windows, or their own file.

Its id stays the same through retakes, so the window keeps its card, while take counts the images. The service holds the image itself, we only keep what the window shows about it.

Vars
attachment_id	The service's id for the image it holds
check_until	When we stop polling for the service's check of the image
id	The window's id for this picture, the same through retakes
image_state	The service's state for the image it holds - processing, ready or failed
pending	What's happening to a new image the service doesn't have yet - rendering, waiting or uploading
preview_seen	Whether the window showed the reporter this image, needed to switch a private picture back to public
public_consent	Whether the reporter lets the image go public with the issue
reason	Why the picture failed, for the window's words - nothing, render, invalid or unconfirmed
source	Where it comes from - view, window or file
take	Which image this is, counting retakes, so the window never shows the last one's preview
taken_at	When the current image was taken, in REALTIMEOFDAY
title	The captured window's title, for a window capture
Procs
card_source	What the window's card for this picture is made from - its age goes by when it was taken, which only a new take moves
forget_image	Forgets the image the service held, so the picture waits on a new one
image_unclaimed	Whether the service may hold an image this picture sent under an id we never heard, as a lost upload reply leaves it
update_attachment	Takes the service's view of the image, returning whether it just became ready. Uploads and polls keep our sharing choice; submission sends it with the attachment id.
window_data	The picture as the window sees it, with how long ago it was taken in ms

Var Details

var
attachment_id

The service's id for the image it holds

var
check_until

When we stop polling for the service's check of the image

var
id

The window's id for this picture, the same through retakes

var
image_state

The service's state for the image it holds - processing, ready or failed

var
pending

What's happening to a new image the service doesn't have yet - rendering, waiting or uploading

var
preview_seen

Whether the window showed the reporter this image, needed to switch a private picture back to public

var
public_consent

Whether the reporter lets the image go public with the issue

var
reason

Why the picture failed, for the window's words - nothing, render, invalid or unconfirmed

var
source

Where it comes from - view, window or file

var
take

Which image this is, counting retakes, so the window never shows the last one's preview

var
taken_at

When the current image was taken, in REALTIMEOFDAY

var
title

The captured window's title, for a window capture

Proc Details

proc
card_source
()

What the window's card for this picture is made from - its age goes by when it was taken, which only a new take moves

proc
forget_image
()

Forgets the image the service held, so the picture waits on a new one

proc
image_unclaimed
()

Whether the service may hold an image this picture sent under an id we never heard, as a lost upload reply leaves it

proc
update_attachment
(/list/attachment, update_consent)

Takes the service's view of the image, returning whether it just became ready. Uploads and polls keep our sharing choice; submission sends it with the attachment id.

proc
window_data
()

The picture as the window sees it, with how long ago it was taken in ms

bug_report_picture /datum/bug_report_picture

Vars

Procs

Var Details

var attachment_id

var check_until

var id

var image_state

var pending

var preview_seen

var public_consent

var reason

var source

var take

var taken_at

var title