Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Won't Fix
-
Affects Version/s: Current Version
-
Fix Version/s: Current Version
-
Component/s: OIOIOI
-
Labels:None
Description
It would be very useful if the submit view automatically selected the task for which the user did the last submit in current contest. The motivation for this is:
1. If the user is going to submit a solution to the new task, he/she is going to pay attention to selecting the proper problem.
2. If the user is going to resubmit (possibly n-th time) the solution, he/she is less likely to pay attention to selecting the problem and hence is much more likely to submit the solution to the wrong task.
Now the scenario in 2 is pretty frustrating for the user, because I can imagine some ranking views which take into account the time of the first submission/last submission/number of submissions of a task. Mistakingly submitting code with no option to revert this and therefore - losing points by a very stupid mistake is a situation of which the odds should be minimized by the system as much as possible.
1. If the user is going to submit a solution to the new task, he/she is going to pay attention to selecting the proper problem.
2. If the user is going to resubmit (possibly n-th time) the solution, he/she is less likely to pay attention to selecting the problem and hence is much more likely to submit the solution to the wrong task.
Now the scenario in 2 is pretty frustrating for the user, because I can imagine some ranking views which take into account the time of the first submission/last submission/number of submissions of a task. Mistakingly submitting code with no option to revert this and therefore - losing points by a very stupid mistake is a situation of which the odds should be minimized by the system as much as possible.
Activity
This explanation seems reasonable. It would be good to bring the patch enabling the last change in the topic to SZKOpuł, but that's not relevant to this issue or this discussion.
I'm closing the issue.
I'm closing the issue.
Show
Tomasz Zakrzewski
added a comment - This explanation seems reasonable. It would be good to bring the patch enabling the last change in the topic to SZKOpuł, but that's not relevant to this issue or this discussion.
I'm closing the issue.
Tomasz Zakrzewski
added a comment - This explanation seems reasonable. It would be good to bring the patch enabling the last change in the topic to SZKOpuł, but that's not relevant to this issue or this discussion.
I'm closing the issue. Tomasz Zakrzewski
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Resolved [ 5 ] |
| Assignee | Tomasz Zakrzewski [ tommalla ] | Szymon Acedański [ accek ] |
| Fix Version/s | Current Version [ 11000 ] | |
| Resolution | Won't Fix [ 2 ] |
Szymon Acedański
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
1h 41m | 1 | Tomasz Zakrzewski | 2013-11-23 14:51 | |||||
|
310d 5h 50m | 1 | Szymon Acedański | 2014-09-29 21:41 |
Also for team contests the user may not notice that another team member submitted something and changed this default.
That's why we recently added the functionality to not have any problem selected in the submission form, forcing all users to consciously choose the proper task.