Skip to content

Renaming a NoNode-ed COMP requires uncook-recook #49

Open

Description

@function-store

Seems like dependency is not updated, as well as the extension still remaining in TD memory and somehow still calling from/to the non-existing comp???

Activity

  1. changed the title [-]Renaming a QuickExt-ed COMP requires re-init[/-] [+]Renaming a QuickExt-ed COMP requires uncook-recook[/+] on Oct 28, 2024
  2. function-store commented on Oct 28, 2024

    @function-store
    OwnerAuthor

    hmm so an OP's .id attribute doesn't change between renames... 😃 but it does if you move it somewhere else
    and since extensions reinit when a comp is moved, maybe I can just cache this id instead of the reference to the clearly non-existent ghost OP after a rename

  3. changed the title [-]Renaming a QuickExt-ed COMP requires uncook-recook[/-] [+]Renaming a NoNode-ed COMP requires uncook-recook[/+] on Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingderivativeSomething I gotta ask Derivative about or put in an RFE

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions