Deken and plugin managing problem

[arno-arno]

In PlugData v0.6.2 on Windows there is some problem with deleting and adding plugins via deken. Both as a vst plugin and standalone app.
It seems to don't remember installed plugins after restarting app if plugin was installed if I don't add it to path.
Even if I add it to path I can install it every time after restarting PlugData.
There is also no way to uninstall cyclone, else or any other plugins I had install via deken, because deken don't see installed plugins. Even when I delete folders with cyclone and else this both libraries are always in Plug Data.
This is how it looks after installing the plugin:

This is how it looks after restarting PlugData:

This is how it looks when I search for the installed plugin:

[timothyschoen]

Thanks for reporting!

You can't install ELSE and cyclone, because they are baked into PlugData. It's the only way I can have them work inside a plugin :(

It should remember the installed packages though, that is definitely a bug.

[arno-arno]

Thanks for the response! I think there is something wrong with path management. Searching is for the whole files tree, not for specific directory. For example:
1.Create directory called foo and file output~.pd in this
2.Create directory called bar in foo directory and also output~.pd file
3.Add directory foo to search path

Vanilla Pd would search for pd only in foo directory. If I would access the output~.pd from the bar directory I need to type [bar/output~].
PlugData v0.6.2 will search the foo directory, but also bar, so there will be a conflict.

[timothyschoen]

You're right, the paths are currently configured to be recursive, which causes issues. I'm going to rewrite the whole path management for v0.7.0 because the whole thing is a total mess.

I'm unable to reproduce the problem with Deken though, on Windows the installed externals don't disappear after restarting for me. Could you try a recent build (from the Actions tab, or manually built) to see if it's working now?

[Yzrsah]

I became suspicious and checked this because I found countless little things break when trying to use a non-Administrator account on Windows. In this case the packages disappear after restart if you're logged in on a non-Administrator account but it works correctly if you're logged in on the admin account.

[timothyschoen]

I became suspicious and checked this because I found countless little things break when trying to use a non-Administrator account on Windows. In this case the packages disappear after restart if you're logged in on a non-Administrator account but it works correctly if you're logged in on the admin account.

Thanks for figuring that out, I never would have thought of that! I'll see what I can do about it. Can only the admin user write to %APPDATA%?

[Yzrsah]

@timothyschoen I didn't find anything odd with filesystem or permissions. The non-admin has full permission to write to their %AppData% and PlugData is downloading Deken files correctly and saving to %AppData%/Roaming/plugdata/Deken and .pkg_info is being written there.

But when you're logged in as a non-admin they don't show up in Plugdata after restart. Possibly something that returns a path is returning the wrong location. I thought maybe it was getting the wrong AppData directory so I tried installing Deken packages on the admin account's PlugData then switching back to the non-admin, but the Deken list is still empty.

[timothyschoen]

Now that we've moved plugdata's files from %APPDATA%/plugdata to User/Documents/plugdata, I suspect this is now solved.

Let me know if it isn't, I'll reopen the issue.