Skip to content

nitpick refactor: Use automerge cursor instead of OT for multiplayer cursor tracking #113

@vezwork

Description

@vezwork

#94 seems like a good solution for cursor tracking.... but..... Nit: Instead, I think it may simplify code and be a bit more robust to use https://automerge.org/automerge/automerge/struct.Cursor.html

This would mean creating a automerge cursor from position whenever we receive a multiplayer cursor update and letting it hang about, syncing monaco cursors to it, until another multiplayer cursor update comes through and we replace the automerge cursor with a new one.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions