Manually Deleted Plugins Don't Show in Available

Issue #33 on hold
Donovan Keith created an issue
  1. Install a plugin w/ CV Toolbox
  2. Delete the plugin installation
  3. BUG: Plugin is not listed in available

The "Available Plugins" cache needs to be rebuilt every time CV Toolbox is manually launched.

Comments (7)

  1. Rick Barrett

    Hmm. Added an option to check for the path in the installLog with 0c06f53df1a but realized I'm only storing the base folder name in the installLog. Especially since some resources don't go in a subfolder I'll have to store the path to each file that's installed.

    If I check every individual file though, that could take awhile and be prone to errors if the plugin manipulates the files in its own directory.

    I could just check the first file for each plugin, but there's no guarantee that's an 'important' file (it could be a readme).

  2. Rick Barrett

    As of a0ecd3f7, I'm checking the first absolute file that was extracted. This is not symbolic-link friendly, and not necessarily 100% accurate, but it's what I've got until I've got a better idea.

  3. Donovan Keith reporter

    Even without symbolic links this doesn't seem to be functioning. Try installing CV-SwIm then manually delete it. You won't be able to reinstall it with CV-Toolbox.

  4. Donovan Keith reporter

    It might not be possible with Library files, but I still think a plugin ID check isn't the worst temporary solution - especially considering we aren't hosting any lib files at the moment.

    --edit--

    Just realized that scripts & pipe-works can't be solved with Plugin ID.

    Perhaps CV Toolbox could write a token of some kind into the files' metadata and check for its existence?

    If the concern is that checking for installed plugins that have been removed will take a while, you could create a "Refresh list of installed tools" command that allows the user to manually refresh the list after uninstalling along with a pinwheel/hourglass.

  5. Rick Barrett

    The verification was broken. Should be fixed with 4e0d034. Note that it still only checks the first installed file and has to be manually invoked from the File menu.

  6. Log in to comment