Don't send busy respond message when to_id is null, it will confuse the respondee
This commit is contained in:
@@ -2230,7 +2230,7 @@ void process_improved_im(LLMessageSystem *msg, void **user_data)
|
|||||||
{
|
{
|
||||||
if (!gIMMgr->hasSession(session_id) || gSavedPerAccountSettings.getBOOL("AscentInstantMessageResponseRepeat"))
|
if (!gIMMgr->hasSession(session_id) || gSavedPerAccountSettings.getBOOL("AscentInstantMessageResponseRepeat"))
|
||||||
{
|
{
|
||||||
busy_message(msg, from_id);
|
if (to_id.notNull()) busy_message(msg, from_id);
|
||||||
}
|
}
|
||||||
|
|
||||||
// now store incoming IM in chat history
|
// now store incoming IM in chat history
|
||||||
|
|||||||
Reference in New Issue
Block a user