On Sat, Mar 1, 2008 at 3:12 AM, John Gilmore [EMAIL PROTECTED] wrote:
Hmmm, so if my activity needs it's preferences before it can display
anything to the user, potential future lazy loading of the data-store
(to try and speed up general activity start-up time) is going to leave
folks
On Thu, Feb 28, 2008 at 10:56 PM, Gary C Martin [EMAIL PROTECTED] wrote:
It does seem like read_file() is only triggered if you have
previously
saved an actual file to filesystem, if you just have metadata, no
call
is ever made to read_file() so it's a rather bad place to pick-up the
Hmmm, so if my activity needs it's preferences before it can display
anything to the user, potential future lazy loading of the data-store
(to try and speed up general activity start-up time) is going to leave
folks watching my activity with a blank screen for a lazy while? Ouch.
Ahem.
Hi Tomeu,
On 28 Feb 2008, at 09:40, Tomeu Vizoso wrote:
Well, __init__ is too soon.
Well before calling activity.Activity.__init__(self, handle) yes that
would be a real bad idea for sure :-) but after that it 'should' be
fine shouldn't it, as the activity class is all set up? I can
On Thu, Feb 28, 2008 at 12:45 PM, Gary C Martin [EMAIL PROTECTED] wrote:
Hi Tomeu,
On 28 Feb 2008, at 09:40, Tomeu Vizoso wrote:
Well, __init__ is too soon.
Well before calling activity.Activity.__init__(self, handle) yes that
would be a real bad idea for sure :-) but after that it
It does seem like read_file() is only triggered if you have
previously
saved an actual file to filesystem, if you just have metadata, no
call
is ever made to read_file() so it's a rather bad place to pick-up the
metadata. At least this is what I'm seeing here – I've just created a
0
Hope this is not too silly a question, but is the read_file() method
always called after the Python activity __init__'? I'm just started
using self.metadata to store some basic preferences to pickup after a
Journal resume, but I'm finding read_file() is never called in my
activity. My
