On Fri, Sep 3, 2010 at 23:59, Bernie Innocenti ber...@codewiz.org wrote:
El Fri, 03-09-2010 a las 11:23 -0400, Martin Abente escribió:
Well, thats true in theory, assuming all the activities are properly
designed for sugar. In the field you already know thats not the case.
Also... even when
Excerpts from Bernie Innocenti's message of Fri Sep 03 01:46:02 +0200 2010:
I thought almost all activities understood the protocol for quitting
cleanly (probably a dbus message). You can test it by clicking Stop from
the menu on the icons top of the frame. That wouldn't work without
sending
On Fri, 03 Sep 2010 01:46:02 +0200, Bernie Innocenti ber...@codewiz.org
wrote:
El Thu, 02-09-2010 a las 09:26 -0400, Martin Abente escribió:
Weird, I really tried to trigger it on our last Dextrose build and
never
happened.
Perhaps it's gone, but I have not done anything to fix it. The bug
On Fri, Sep 3, 2010 at 11:23 AM, Martin Abente
mabe...@paraguayeduca.org wrote:
for sugar. In the field you already know thats not the case. Also... even
when
the activities are being implemented in python through the Activity Class,
the
read and write methods needs to be implemented by the
El Fri, 03-09-2010 a las 11:23 -0400, Martin Abente escribió:
Well, thats true in theory, assuming all the activities are properly
designed for sugar. In the field you already know thats not the case.
Also... even when the activities are being implemented in python
through the Activity Class,
Weird, I really tried to trigger it on our last Dextrose build and never
happened.
The whole idea of killing activities is a little bit controversial I
think, you have to assume to many things about activities, so far just a
few activities in sugar uses all the proper mechanisms, I am afraid that
6 matches
Mail list logo
