Commit f42103f
committed
fix: refresh Family Events tab when participant is renamed
After editing a family member (eg the father) from within the Family editor
and saving, the embedded Events tab must refresh to show the participant's
current name in the "Main Participants" column. Currently, the person-update
signal is routed to topdata_updated (editfamily.py:507), which calls load_data
(editfamily.py:579–586) to refresh only the top father/mother panel. The
embedded event list is never rebuilt, so its "Main Participants" column keeps
showing the stale name.
Route person-update to a new handler person_updated that calls both
topdata_updated (preserving the existing top-panel refresh) and
event_list.rebuild_callback (to rebuild the event-list model). This mirrors
the pattern already used by the Children tab in the same editor (editfamily.py:
179, 185–190), which listens for person-update and calls rebuild. The fix
reuses rebuild_callback, the same entry point that event-update already uses
(eventembedlist.py:152–158), so no new API is introduced.
Implementation spans two hunks in editfamily.py: signal mapping at line 509,
and a new person_updated method at lines 588–602. A hasattr guard protects
against person-update firing before _create_tabbed_pages constructs the tab.
Fixes #8603
Signed-off-by: Eduard Ralph <eduard@ralphovi.net>1 parent 0d9e148 commit f42103f
1 file changed
Lines changed: 17 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
504 | 504 | | |
505 | 505 | | |
506 | 506 | | |
507 | | - | |
| 507 | + | |
508 | 508 | | |
509 | 509 | | |
510 | 510 | | |
| |||
585 | 585 | | |
586 | 586 | | |
587 | 587 | | |
| 588 | + | |
| 589 | + | |
| 590 | + | |
| 591 | + | |
| 592 | + | |
| 593 | + | |
| 594 | + | |
| 595 | + | |
| 596 | + | |
| 597 | + | |
| 598 | + | |
| 599 | + | |
| 600 | + | |
| 601 | + | |
| 602 | + | |
| 603 | + | |
588 | 604 | | |
589 | 605 | | |
590 | 606 | | |
| |||
0 commit comments