summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
Diffstat (limited to 'include')
-rw-r--r--include/m_chat.h2
-rw-r--r--include/m_chat_int.h2
2 files changed, 3 insertions, 1 deletions
diff --git a/include/m_chat.h b/include/m_chat.h
index 51ca20a9b3..0845defe19 100644
--- a/include/m_chat.h
+++ b/include/m_chat.h
@@ -232,7 +232,7 @@ struct GCSESSION
and what session it is related to. The GCDEST structure and its members are ALWAYS
used (but the members can be NULL in some occasions). Depending on what type of event
you are sending, the members of GCEVENT have different usage. Each event and how to
- use the members are discussed below. The "bAddToLog" and "time" members are always valid
+ use the members are discussed below. The "AddToLog" and "time" members are always valid
and always mean the same. bAddToLog = TRUE means that the event is added to the disk log
(at least when this makes sense). This can be used by Jabber for instance, when
it needs to add channel history to the window, but without logging to disk.
diff --git a/include/m_chat_int.h b/include/m_chat_int.h
index 34affee3d5..4b8c95acfb 100644
--- a/include/m_chat_int.h
+++ b/include/m_chat_int.h
@@ -399,6 +399,8 @@ struct CHAT_MANAGER
HANDLE hBuildMenuEvent, hSendEvent;
FONTINFO aFonts[OPTIONS_FONTCOUNT];
SESSION_INFO *wndList;
+ int *logIconBmpSize;
+ PBYTE *pLogIconBmpBits;
// user-defined custom callbacks
void (*OnCreateModule)(MODULEINFO*);