- Change Summary:
-
rebased
- Commits:
-
Summary ID 830c64f6659ea19ddc57a44658492f074c591ffa ce022af5655717f2da906b317c9cd5447de766bd
Move conversation management from gtkconv.c to PidginConversationWindow.
Review Request #1108 — Created Oct. 28, 2021 and submitted
This replaces the conversation window's notebook with a treeview and is the first steps in keeping conversations alive even when they're closed in the Pidgin ui.
Opened an im, closed the window, opened the same im again. Opened multiple ims and a chat, verified all functioned as expected.
Summary | ID |
---|---|
bea831d8f9f7a4200fc96af25b7b91d6f34317f4 |
Description | From | Last Updated |
---|---|---|
instead? |
QuLogic | |
Does pidgin_conversation_window_foreach_destroy effectively empty the tree model? Dispose may be called multiple times, so we should be certain we're safe … |
QuLogic | |
Comparing to e.g., GtkStack, there is a visible-child property, and you can use a notify signal for this. Do we … |
QuLogic | |
Double semicolon. |
QuLogic | |
Surely we don't need to name it purplewin (considering it's a PidginConversationWindow) now that all the lines with it have … |
QuLogic |
- Change Summary:
-
rebased
- Commits:
-
Summary ID ce022af5655717f2da906b317c9cd5447de766bd 2835561522dc315dc01ee250580038c8d031c52c
- Change Summary:
-
rebased
- Commits:
-
Summary ID 2835561522dc315dc01ee250580038c8d031c52c 37776707eb10ee3aab6065e58e7c6fb20f0bcfcc
- Change Summary:
-
rebased
- Commits:
-
Summary ID 37776707eb10ee3aab6065e58e7c6fb20f0bcfcc 0b483f227502533e5f17a7bae113d6da90d475f2
-
-
-
Does
pidgin_conversation_window_foreach_destroy
effectively empty the tree model? Dispose may be called multiple times, so we should be certain we're safe to calling this again. -
Comparing to e.g.,
GtkStack
, there is avisible-child
property, and you can use a notify signal for this. Do we want to do something like that? -
-
Surely we don't need to name it
purplewin
(considering it's aPidginConversationWindow
) now that all the lines with it have changed?