Timestamp is improperly set #4

New Issue

2024-07-06T02:09:27-06:00

sashakoshka commented

2024-07-06 02:09:27 -06:00

NewClaim does not properly set the timestamp for when the selection was gained, instead using 0 (CurrentTime). It should instead use the timestamp of the event that caused the selection to be gained. We can't modify NewClaim to take in a timestamp parameter for two reasons:

The API is stable
We should still use CurrentTime when the claim was not triggered by an input event

Instead, we should create a different constructor that takes in a timestamp. Possibly NewClaimWithTimestamp or something.

NewClaim does not properly set the timestamp for when the selection was gained, instead using 0 (CurrentTime). It should instead use the timestamp of the event that caused the selection to be gained. We can't modify NewClaim to take in a timestamp parameter for two reasons: 1. The API is stable 2. We should still use CurrentTime when the claim was not triggered by an input event Instead, we should create a different constructor that takes in a timestamp. Possibly NewClaimWithTimestamp or something.

sashakoshka referenced this issue from a commit

2024-07-06 20:32:06 -06:00

Add NewClaimWithTimestamp

sashakoshka closed this issue

2024-07-06 20:32:09 -06:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: tomo/xgbsel#4