I’m aware of the mapping problem selections have, but I haven’t had a chance to look into it seriously. I’m kind of waiting to see if Andrew will address the problem on Rack’s end. If not, I hope to eventually support mappings.
I wonder if some other programmers around here can help me to understand what approach stoermelder is taking to address the problem.
So I just updated to latest VCV Rack, and the installer completely blew away the install directory that had my development checkout of Prefabs so I just lost all the work I was doing.
But the upshot is that I’m now able to reproduce the on-close crash. I’ll start looking into it once I get everything set up again.
i have tried several times, not working here, whenever i try to add the strings with my patches dir, nothing happens inside vcv, patches dir is not searched nor visualized, and when i come back to prefabs.json it seems to be reverted to the default…
win 7, vcv 2.2.2, prefabs build 2.0.4
Wow, thanks! That fixed it. What a wonderful idea you’ve had- I find it much easier to drill down into the mass of modules to find one that does what I’m thinking of at the moment.
A previous version loaded on my machine, but the 2.0.5-nightly does not. On macOS 10.12.5:
[1.040 warn src/plugin.cpp:237 loadPlugin] Could not load plugin /Users/lab/Documents/Rack2/plugins/Prefabs: Failed to load library /Users/lab/Documents/Rack2/plugins/Prefabs/plugin.dylib: dlopen(/Users/lab/Documents/Rack2/plugins/Prefabs/plugin.dylib, 6): Symbol not found: __ZNKSt3__14__fs10filesystem4path6__stemEv
Referenced from: /Users/lab/Documents/Rack2/plugins/Prefabs/plugin.dylib
Expected in: /usr/lib/libc++.1.dylib
in /Users/lab/Documents/Rack2/plugins/Prefabs/plugin.dylib
The code I’m using to process files now requires macOS 10.15. I guess it’s a lot to ask people to upgrade. I’ll have to figure out which bits are unsupported and I guess figure out other ways to write those parts. I’ll try to do it soon but I’ll be busy tomorrow. macOS 10.15 is four years old now I think.
Ok, but just remember that Rack supports macOS 10.9+ and you’d be suprised how many peopl use older Macs. Maybe look inside the Rack code and/or its osdialog code for suitable and compatible file-processing code?
Is it now required that opening the widget / refresh needs to be done when opening a patch? By default, I’m using the right click menu with widget off.
When I open a patch, seems like I have refresh / open the widget first each time, before the right click menu populates for the first time? Otherwise it’s blank.