Opened 8 years ago

Closed 8 years ago

#4427 closed enhancement (duplicate)

Cookie search (activity) should add functionality to restart or quit when the player has one or lost

Reported by: Rach4d Owned by:
Priority: Unspecified by Maintainer Milestone: Unspecified
Component: untriaged Version: 0.98.x
Severity: Unspecified Keywords: cookie, activity, activities, search
Cc: walter Distribution/OS: Ubuntu
Bug Status: New

Description

As it stands now the game continues after the player has won or lost, allowing them to continue clicking on the cookie widgets even though the game has ended. I have created this new functionality and have attached the 'game.py' file. Simply replace the game.py file in the CookieSearch.activities folder with the one attached.

Attachments (1)

game.py (13.0 KB) - added by Rach4d 8 years ago.
Replace the game.py file in CookieSearch.activity with this game.py for new functionality.

Download all attachments as: .zip

Change History (6)

Changed 8 years ago by Rach4d

Replace the game.py file in CookieSearch.activity with this game.py for new functionality.

comment:1 Changed 8 years ago by erikos

  • Cc walter added

Hi Rach4d, thanks for filing the bug. I do not know about this game, and there is no component called 'cookie' in the sugarlabs bug tracker. Can you point to the activity? Maybe that will tell.

Water do you know more about that?

comment:2 follow-up: Changed 8 years ago by walter

Erikos: this is one of my activities. I never asked for a comment to be made for it. Maybe we need a general Sugar activity component for such cases.

Rach4d: thanks for the patch. I'll look at it in the next day or two.

regards.

-walter

comment:3 in reply to: ↑ 2 Changed 8 years ago by erikos

Replying to walter:

Erikos: this is one of my activities.

Yes, figured that by the copyright in the patch :)

I never asked for a comment to be made for it. Maybe we need a general Sugar activity component for such cases.

There is the "ActivityTeam" component, but afaik this is just for activities maintained by the activity team. This case would be slightly different though. The main question is, who would be tracking a 'Sugar activity component', there is nothing worse than expectations that can not be fulfilled :)

comment:4 Changed 8 years ago by walter

Since most of the buggy activities are mine, I volunteer to be the one to get the tickets.

The more difficult issue I think is discoverability in Trac of what component to assign as the list gets longer and longer.

comment:5 Changed 8 years ago by walter

  • Resolution set to duplicate
  • Status changed from new to closed

See patch attached to #4424

Note: See TracTickets for help on using tickets.