The reason I don't report bugs most of the time...

[nandblock]

... is something very small but annoying. If I want to report a bug I need to give a specific table (even when the bug is just about any game of that type). There is no direct link from the table to create a bug. So I need to cut and paste 2 strings of text: (1) the table number; (2) the error message that appears onscreen. And often I need to copy a 3rd piece of info, the move number. It is possible for me to do all this, sure, but it's enough keystrokes I can't usually be bothered unless I'm particularly irked by a bug.

Suggestion: Simply have a button "Report a bug on this table" which will create a new bug report with the table number and the move number automatically copied into it.

The obvious problem here I can see is that eliminating the in-between steps could lead to the creation of duplicate reports.

[Giordano Bruno 1974]

The obvious problem here I can see is that eliminating the in-between steps could lead to the creation of duplicate reports.

Not if the button is removed and replaced with "bug already reported" when clicked on.

[Jest Phulin]

Not if the button is removed and replaced with "bug already reported" when clicked on.

Just curious, how would this be implemented? If the computer could identify when a bug happens, it could notify the developer where the bad code was. The idea of bugs, though, is code not behaving how the developer should have made it.

[Giordano Bruno 1974]

Not if the button is removed and replaced with "bug already reported" when clicked on.

Just curious, how would this be implemented? If the computer could identify when a bug happens, it could notify the developer where the bad code was. The idea of bugs, though, is code not behaving how the developer should have made it.

The report button can be there at all the time. If there is no bug then the player doesn't click on it. THe computer doesn't need to work out if there has been a bug or not.

[Tisaac]

Not if the button is removed and replaced with "bug already reported" when clicked on.

Just curious, how would this be implemented? If the computer could identify when a bug happens, it could notify the developer where the bad code was. The idea of bugs, though, is code not behaving how the developer should have made it.

The report button can be there at all the time. If there is no bug then the player doesn't click on it. THe computer doesn't need to work out if there has been a bug or not.

Then why are you talking about " Not if the button is removed and replaced with "bug already reported" when clicked on.".
You could very well encounter several different bugs during the same game, so the button need to stay during the whole game.

[Giordano Bruno 1974]

Just curious, how would this be implemented? If the computer could identify when a bug happens, it could notify the developer where the bad code was. The idea of bugs, though, is code not behaving how the developer should have made it.

The report button can be there at all the time. If there is no bug then the player doesn't click on it. THe computer doesn't need to work out if there has been a bug or not.

Then why are you talking about " Not if the button is removed and replaced with "bug already reported" when clicked on.".
You could very well encounter several different bugs during the same game, so the button need to stay during the whole game.

Because bugs should be reported at the end of the game. Once someone has done so then remove the button so that no-one submits a duplicate report.