| Summary: | the last state of groups should be restored | ||
|---|---|---|---|
| Product: | [Unmaintained] telepathy | Reporter: | Alin M Elena <alinm.elena> |
| Component: | contactlist | Assignee: | Telepathy Bugs <kde-telepathy-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | mklapetek |
| Priority: | NOR | ||
| Version: | git-latest | ||
| Target Milestone: | 0.4.0 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Alin M Elena
2011-05-21 18:13:27 UTC
After spending some time on this bug, I came to conclusion, that this is not an easy/straightforward task. I can save the expand state per group, no problem. But I can't easily reuse it on new contact list window, because I have no way of telling, that the model finished reading all the data (and in fact it never does). So the solution would be to connect to rowsInserted() signal and then check if that row is a group and if so then check the config and expand it accordingly. But that would be active for all newly added groups, ie. after some time you connect some account with group "G1", which is saved to be expanded. So the rowsInserted() will be emitted, the group name will be checked and the group itself expanded. The problem is, that it may feel like an unconsistent behaviour - only some groups are expanded of the newly connected account and some are not. The user might think - what the heck? Why not all of my groups are expanded? (He might have forgotten that he had this group expanded some time ago) So how to actually do this? *** This bug has been marked as a duplicate of bug 277216 *** |