[GH-ISSUE #1306] [Feature Request] Double click should be represented with blue spot #3444

New issue

Open

opened 2026-03-01 19:11:44 +03:00 by kerem · 0 comments

kerem commented 2026-03-01 19:11:44 +03:00

Owner

Copy link

Originally created by @joniale on GitHub (Apr 23, 2024).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/1306

Originally assigned to: @NickeManarin on GitHub.

Normally I cannot distinguish between a click and a double click on the recorded screen. It would be easy and very useful to just change the colour of the spot for double clicks detected by the system.

The solution would be to get the double click event from the system and represent a spot with a different colour, e.g. blue. That way it will not mix with the yellow and red spots that already exist for left and right mouse clicks.

Other colours could also be used.

Originally created by @joniale on GitHub (Apr 23, 2024). Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/1306 Originally assigned to: @NickeManarin on GitHub. Normally I cannot distinguish between a click and a double click on the recorded screen. It would be easy and very useful to just change the colour of the spot for double clicks detected by the system. The solution would be to get the double click event from the system and represent a spot with a different colour, e.g. blue. That way it will not mix with the yellow and red spots that already exist for left and right mouse clicks. Other colours could also be used. <img width="366" alt="image" src="https://github.com/NickeManarin/ScreenToGif/assets/16894469/1a9b7efd-76fc-41c8-91e3-a8763b2a623c">

kerem added the

🔷Enhancement

⬜ Pending

labels 2026-03-01 19:11:44 +03:00

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

dev

v2.40

2.43.1

2.43

2.42.1

2.42

2.41.5

2.41.4

2.41.3

2.41.2

2.41.1

2.41

2.40.1

2.40

2.39

2.38.1

2.38

2.37.2

2.37.1

2.37

2.36

2.35.4

2.35.3

2.35.2

2.35.1

2.35

2.34.1

2.34

2.33.1

2.33

2.32.1

2.32

2.31

2.30.1

2.30

2.29.1

2.29

2.28.2

2.28.1

2.28

2.27.3

2.27.2

2.27.1

2.27

2.26.1

2.26

2.25

2.24.2

2.24.1

2.24

2.23.2

2.23.1

2.23

2.22.1

2.22

2.21.2

2.21.1

2.21

2.20.4

2.20.3

2.20.2

2.20.1

2.20

2.19.3

2.19.2

2.19.1

2.19

2.18

2.17.1

2.17

2.16

2.15.2

2.15.1

2.15

2.14.1

2.14

2.13.3

2.13.2

2.13.1

2.13

2.12.1

2.12

2.11

2.10

2.9

2.8.1

2.8

2.7.3

2.7.2

2.7.1

2.7

2.6

2.5

2.4

2.3.2

2.3.1

2.3

2.2

2.1

Labels

Clear labels   

copy cats

  

duplicated

  

future feature

  

pull-request

Mirrored from GitHub Pull Request

  

⬜ Accepted

  

⬜ Completed

  

⬜ Help Wanted 💪

  

⬜ In Progress

  

⬜ Missing Details

  

⬜ Pending

  

⬜ Waiting For Answer ⏳

  

🆕 feature preview

  

🔷 Bug 🐛

  

🔷 Out Of Scope

  

🔷 Out Of Scope

  

🔷 Question

  

🔷Enhancement

  

🔷Enhancement

  

🔷Invalid / External

  

🔷Knowledge Base

  

🔷Won't Fix

  

🕑 High

  

🕑 High

  

🕑 High

  

🕕 Medium

  

🕙 Low

  

🕛 Critical

No labels

copy cats

duplicated

future feature

pull-request

⬜ Accepted

⬜ Completed

⬜ Help Wanted 💪

⬜ In Progress

⬜ Missing Details

⬜ Pending

⬜ Waiting For Answer ⏳

🆕 feature preview

🔷 Bug 🐛

🔷 Out Of Scope

🔷 Out Of Scope

🔷 Question

🔷Enhancement

🔷Enhancement

🔷Invalid / External

🔷Knowledge Base

🔷Won't Fix

🕑 High

🕑 High

🕑 High

🕕 Medium

🕙 Low

🕛 Critical

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ScreenToGif#3444

No description provided.