sugarlabs / across-and-down-activity Goto Github PK

Resize causes execution recursion, may eventually fail, and leaves a process running after stop.

While in the Pygame main loop run(), a display resize event is handled by Gtk.main_iteration() which calls __configure_cb which calls run() again.

Can be proven by adding a traceback in the size-changed handler;

    def __configure_cb(self, event):
        import sys, traceback
        print traceback.print_stack(file=sys.stderr)
        ...

Activity process keeps running because there is only one QUIT event and the going state is local to each instance of run().

These buttons are not fully visible with screen resolution 1360x669 pixels.

See description of https://github.com/orgs/sugarlabs/projects/5 for reference

Current version in ASLO is 24 dated October 29, 2011.
Version here is still 24 despite the documented chantes.
Since these chantes have not been published, a simple increment to 25 may be sufficient,
appropriately tagged and published to ASLO.

Sugar Fructose activities mostly have a README.md in their repository which can be used as an example. Specific to Across and Down, the README.md should mention the dependency on Sugargame and how development sources are shared. Our failure to do this led a contributor into a blind alley.