[Research] Store strokes in efficient data structure rather than array #23

New Issue

2025-12-29T05:19:04+01:00

adam commented

2025-12-29 05:19:04 +01:00

Originally created by @dscyrescotti on GitHub (May 26, 2024).

Originally assigned to: @dscyrescotti on GitHub.

Description

So far, all strokes are stored in the array and it leads to inefficiency at searching or retrieving strokes for rendering. So, it is a call to replace the existing array with more efficient data structure.

Reference

https://www.youtube.com/watch?v=hUIHtPLL940

Originally created by @dscyrescotti on GitHub (May 26, 2024). Originally assigned to: @dscyrescotti on GitHub. ### Description So far, all strokes are stored in the array and it leads to inefficiency at searching or retrieving strokes for rendering. So, it is a call to replace the existing array with more efficient data structure. ### Reference - https://www.youtube.com/watch?v=hUIHtPLL940

adam closed this issue

2025-12-29 05:19:04 +01:00

adam commented

2025-12-29 05:19:05 +01:00

@dscyrescotti commented on GitHub (May 26, 2024):

It turns out that the implementation of RTree data structure is way complex so GKRTree from GameplayKit is used as temporary. But it will require to build the custom RTree for the project.

@dscyrescotti commented on GitHub (May 26, 2024): It turns out that the implementation of RTree data structure is way complex so GKRTree from GameplayKit is used as temporary. But it will require to build the custom RTree for the project.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/Memola#23