Bug #1218
Channel's un-hidden status doesn't stay between client restarts
100%
Description
To get this effect, you have to follow these steps:
1. Hide channel temporarily
2. Part channel
3. Join channel (it will now be visible again, at the bottom of that network's buffer list)
Optional: talk in the channel, get other people to talk, etc but the buffer must not be blue (new message(s)) when you proceed next
4. Quit the client
5. When you'll restart it, the channel will be temporarily hidden again
Associated revisions
Retains Channel UnHiddens Status after client Restart.
Steps to Reproduce:
1. Hide channel temporarily
2. Part channel
3. Join channel (it will now be visible again, at the bottom of that network's buffer list)
Optional: talk in the channel, get other people to talk, etc but the buffer must not be blue (new message(s)) when you proceed next
4. Quit the client
5. When you'll restart it, the channel will be temporarily hidden again
Root Cause:
After step 3, we are not saving the bufferviewconfig synchronizable object right.
Fix:
Save the bufferviewconfig object correctly.
Fixes #1218.
History
#1 Updated by DevUrandom over 11 years ago
I can confirm this problem using client version 0.8.0.
#2 Updated by ramz about 10 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
Applied in changeset quassel|f5071c58ed73bdacddfe270dfede25b70eb0d363.
Retains Channel UnHiddens Status after client Restart.
Steps to Reproduce:
1. Hide channel temporarily
2. Part channel
3. Join channel (it will now be visible again, at the bottom of that network's buffer list)
Optional: talk in the channel, get other people to talk, etc but the buffer must not be blue (new message(s)) when you proceed next
4. Quit the client
5. When you'll restart it, the channel will be temporarily hidden again
Root Cause:
After step 3, we are not saving the bufferviewconfig synchronizable object right.
Fix:
Save the bufferviewconfig object correctly.
Fixes #1218.