Your source code
Reading what you sent, copying it, downloading it, and sending a corrected version.
Source code on a submission's screen opens what you actually sent, in a window over the screen you were on. It has no address of its own — there is nothing to copy or bookmark, and closing it puts you back.
Whether you may read it is not yours to decide, even though you sent it. Two things take the Source code button off a submission's screen:
- The activity does not share a submission's files with you. Whoever runs it decides which of them a participant may read.
- The round has taken its content back — it is paused with the statements hidden, or it has ended in an activity that closes its finished rounds. The code you wrote against a statement you may no longer read goes with the statement, and comes back with it.
Either way the button is absent, and the screen does not say which of the two it is. Your submission itself stays where it was: it keeps its place in My submissions, its verdict, its score and its per-test results.
It is a full editor, read-only until you say otherwise, with your language's highlighting. A submission carrying several files gets a tab per file; a submission with one shows its name above the editor.
Copy and download
Copy puts the file on screen into the clipboard. Download saves it under its own name. Both act on what is currently displayed — including your unsaved edits, if you have started editing.
Where the activity has the printing module on, a Print button sits beside the others. It asks somebody at a printer for the tab you are looking at, on paper, and it sends what is on screen — including edits you have started and not sent.
It is a copy taken at that moment rather than a link to this submission: what comes out is what you were reading. See Printing your code.
A request naming a submission whose round has taken its content back is refused. A round that will not show you your code will not put it on paper either.
Edit and resubmit
Edit and resubmit unlocks the editor. The button then becomes Send as a new submission.
The original is never rewritten
Sending creates a new submission; this one is left untouched. The submission you are looking at stays exactly as it was judged — same source, same verdict, same score. What you send becomes a new submission, and you land on its screen.
The new submission carries the same declaration the original did — the same problem type and the same language — so it is judged as what it is rather than as whatever a default would have made it.
It is an ordinary submission in every other way: it spends your allowance, it appears in My submissions, and it is refused if the round has stopped accepting.