Project

General

Profile

Actions

Bug #5772

closed

Join / Timestamp not shown in certain config

Added by Myles D 9 months ago. Updated 9 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Interface
Target version:
Start date:
08/17/2023
Due date:
% Done:

0%

Estimated time:
Operative System:
All
Regression:
No

Description

Hi there,

In certain configurations (having all settings checked in Messages -> Joins submenu), and having only "Ignore timestamp for consecutive times" checked from the timestamp options, I have observed two issues that may be related:

1) Joins may still not be shown, because I assume AdiIRC does not count new arrivals as "having been active in the last 10 minutes" yet. Is this intended? It seems like an oversight, because joins always imply activity, no?

2) The Timestamp for a message from that same user in issue 1 (right after joining) is also omitted even though it should have been placed, when "Ignore timestamp for consecutive times" has been checked. Does AdiIRC count timestamps from hidden join messages somehow?


Files

Clipboard-1.png (2.41 KB) Clipboard-1.png Myles D, 08/17/2023 09:50 PM
Actions #1

Updated by Per Amundsen 9 months ago

For 1), this is intended, when "Only show events from users active in the last [X] minutes" is enabled, join/part/nick/quit messages are only shown from users who have spoken in the last X minutes. The ideas behind this feature is users only care what happens to other users they are currently speaking to or reading messages from.

For 2), if you have "Ignore timestamp for consecutive times" enabled, all messages (except the first) with the same timestamp will not have a timestamp. Same timestamp means if you have a 4 messages with the timestamp of [20:44], only the first of these 4 messages have a timestamp. This option affects all types of messages and is purely based on the timestamp itself, while "Ignore timestamp for consecutive messages" only affect user messages from the same user.

There might be a bug here, if I understand correctly, a user joins and imminently sends a message, the join is hidden but the message doesn't have a timestamp. If there is no previous message or event with the same timestamp, then that is a bug. I'll do some tests on that.

Actions #2

Updated by Myles D 9 months ago

Yes, that is exactly right. A user joins, the join message is hidden, and the first message (identical time to the hidden join message, it might matter, or might not) also has its timestamp hidden with settings as shown.

Actions #3

Updated by Per Amundsen 9 months ago

  • Status changed from New to Resolved
  • Operative System changed from Windows 10 to All

I can reproduce, should be fixed in next beta, thanks.

Actions #4

Updated by Per Amundsen 9 months ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF