15 | | > > My issue here is that sometimes debug logs raise the cognitive load too much ''for me'' when I try to read them. |
16 | | > It's too much even for me most of the time. |
17 | | > But every detail that is being logged is there because it means something. |
18 | | > > Also, these extra logs are ~200 lines; in my head, would be seeing 2 lines (or 5 or 10 depending on "how" this works). |
19 | | > I think that the reason you were getting 200 lines was the bug fixed in comment:3. |
20 | | > |
21 | | > Normal clipboard events are 20 lines or so. For example when receiving (simplified pseudo code): |
22 | | > * route the packet to the clipboard handler |
23 | | > * parse packet |
24 | | > * find the callback waiting for this data |
25 | | > * filter the clipboard targets |
26 | | > * convert the clipboard data from wire format to native format |
27 | | > * open OS clipboard (and retry if needed) |
28 | | > * set value |
29 | | > * free resources |
30 | | > |