[Bugs] #428 UNSP: connect('map') to activity widow not to current canvas
SugarLabs Bugs
bugtracker-noreply at sugarlabs.org
Tue Mar 3 19:13:49 EST 2009
#428: connect('map') to activity widow not to current canvas
------------------------------------------+---------------------------------
Reporter: alsroot | Owner: marcopg
Type: defect | Status: reopened
Priority: Unspecified by Maintainer | Milestone: 0.84
Component: sugar-toolkit | Version: 0.83.x
Severity: Unspecified | Resolution:
Keywords: r+ | Distribution: Unspecified
Status_field: Needinfo |
------------------------------------------+---------------------------------
Changes (by wadeb):
* status: closed => reopened
* resolution: fixed =>
Comment:
Ok, I have something to add to this ticket.
What if an activity needs to know *before starting up* whether it is a new
instance or a resumed instance?
Currently, all of my activities set up their new instance state and then
expect it to be clobbered by 'read_file' if this is a resume. But there
are cases where that's not possible or has major issues.
For example, in a Terminal branch this weekend I added saving / restoring
of the terminal state. This requires me to launch the child process
differently depending on whether it's resumed or not. So, I *have* to
know when the activity starts up whether I'm saving or resuming.
I think we should add a 'new_file' callback which is called when
'read_file' *will not* be called.
Also, I think the _file APIs are kind of poorly named. Wouldn't it be
better to have resume_instance, save_instance and new_instance? If it's
agreed, we could add these and then have the default implementations call
read_file, write_file and nothing, respectively.
Regards,
Wade
--
Ticket URL: <http://dev.sugarlabs.org/ticket/428#comment:15>
Sugar Labs <http://sugarlabs.org/>
Sugar Labs bug tracking system
More information about the Bugs
mailing list