>
>
> There's a whole lot of stuff being run after Activity.__init__() before
> the activity is actually "started" (take a look at the source [1]).
> I haven't looked into it closely, but I suspect that your early
> self.close() hangs because the widgets are not set up yet.
>
>
Maybe I should put
On Thu, Feb 10, 2011 at 08:14:08AM +0100, tom.staub...@fhtw-berlin.de wrote:
> Actually this would be a great feature in my opinion.
> To me it happened often enough that an activity got started
> accidentally while dragging and dropping images from the journal to a
> USB Stick, for example.
> Bei
On Feb 9, 2011, at 7:55 PM, Erik Blankinship wrote:
> If I wanted to stop an activity as soon as it was initiated, how would I do
> that? The code below hangs with a grey screen.
>
> Why would I want to do this? I am trying to understand how the sugar code
> base works. This seems like a goo
Excerpts from Erik Blankinship's message of Wed Feb 09 19:55:12 +0100 2011:
> class NotTodayActivity( activity.Activity ):
>
> def __init__( self, handle ):
> activity.Activity.__init__( self, handle )
>
> self._auto_shut_down = False
> if not self.should_this_activit
If I wanted to stop an activity as soon as it was initiated, how would I do
that? The code below hangs with a grey screen.
Why would I want to do this? I am trying to understand how the sugar code
base works. This seems like a good exercise for understanding how sugar
activities start and stop.
5 matches
Mail list logo
