#1474 closed defect (fixed)
Listen for metadata updates in the activity frame
Reported by: | erikos | Owned by: | erikos |
---|---|---|---|
Priority: | Immediate | Milestone: | |
Component: | Sugar | Version: | 0.85.x |
Severity: | Major | Keywords: | 11.2.0 |
Cc: | sascha_silbe | Distribution/OS: | Unspecified |
Bug Status: | Assigned |
Description
- open an activity
- change the title using the entry field of the activity
result: entry in the Journal is updated, the activity palette in the home view is updated, too, the title in the activity palette in the frame is not updated
- open an activity
- change the entry title in the journal
- the activity palette in the home view is updated, the title in the activity palette in the frame is not updated and the title in the activity title box is neither. Even better when closing the activity, the title in the journal is set to the old one.
Looks like a regression to me.
Change History (12)
comment:1 Changed 14 years ago by tomeu
- Component changed from sugar to journal
- Owner changed from tomeu to alsroot
comment:2 Changed 14 years ago by erikos
I thought that it worked before :) Anyhow, at least the second part is not good.
comment:3 Changed 14 years ago by sascha_silbe
- Cc sascha_silbe added
comment:4 in reply to: ↑ description Changed 14 years ago by alsroot
Replying to erikos:
- open an activity
- change the title using the entry field of the activity
result: entry in the Journal is updated, the activity palette in the home view is updated, too, the title in the activity palette in the frame is not updated
thats not a regression(at least from 0.84), but yeah, better to fix it
- open an activity
- change the entry title in the journal
- the activity palette in the home view is updated, the title in the activity palette in the frame is not updated and the title in the activity title box is neither. Even better when closing the activity, the title in the journal is set to the old one.
I guess, thats a core issue of sugar(and not only 0.86),
activity(after opening) caches jobject and if it doesn't track jobject events(I didn't see such activities) after next write_file() it stores cached values and overwrites existed.
comment:5 Changed 14 years ago by alsroot
- Milestone changed from 0.86 to 0.88
about first test case,
alsroot │ tomeu: do you think we should fix first issue of http://bugs.sugarlabs.org/ticket/1474? alsroot │ ..in 0.86 alsroot │ .2 tomeu │ alsroot: I would say depending on the fix * │ alsroot looks to code alsroot │ tomeu: what do you think about adding ds listener to sugar/src/jarabe/model/shell.py:Activity class? to track title │ changes tomeu │ alsroot: sounds good to me tomeu │ alsroot: we should take care of cycles, though alsroot │ tomeu: yeah, thats the original question, can such changes be landed to 0.86 tomeu │ alsroot: don't think so :/ * │ alsroot splits #1474 to two issues and target them to 0.88 tomeu │ that sounds good, yeah
comment:6 Changed 14 years ago by alsroot
second test case is dup of #1358
comment:7 Changed 14 years ago by erikos
- Bug Status changed from Unconfirmed to Assigned
- Component changed from journal to sugar
- Owner changed from alsroot to erikos
- Status changed from new to assigned
- Summary changed from Inconsitency when changing journal entry name to Listen for metadata updates in the activity frame
This ticket will now handle the activity frame update. Look for the Journal one in #1358.
comment:8 Changed 14 years ago by sascha_silbe
What's the status of this? Will we fix the frame for 0.88 or stall to 0.90?
comment:9 Changed 14 years ago by erikos
- Milestone changed from 0.88 to 0.90
- Severity changed from Blocker to Major
No fix for this one yet, so I guess we will move it to 0.90. It is not a blocker after all.
comment:10 Changed 13 years ago by erikos
- Keywords 11.2.0 added
comment:11 Changed 12 years ago by erikos
- Resolution set to fixed
- Status changed from assigned to closed
I'm not so sure it's a regression, but surely something good to have fixed.