On Nov 15, 2011, at 3:19 AM, IOhannes m zmoelnig wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 2011-11-15 03:48, Richie Cyngler wrote: >> Thanks Hans, >> >> Done. The console still shows Gem 0.92.3. But I don't know how to test >> which one is actually running when I use Gem objects. I'm assuming it's >> still the old one. > > if it shows "0.92.3" than it most likely is 0.92.3 > > elaborated guess: > Gem does a bit of path magic to be able to access its own abstractions. > this means that it adds it's own path to the list of search paths of Pd. > if you then manually edit your search paths and save, you will end up > with a hardcoded path to the currently installed version of Gem. > if you now install a new Gem into a different location, you still have > the old search path stored in your preferences, and Pd is likely to look > there first, thus finding and loading the old Gem! > > short fix: > open your "Path"-preferences and delete all references to the Gem-paths. > save. > restart Pd
I generally recommend not using the preferences with Pd-extended and instead store the settings in the patch and use the standard install locations. .hc ---------------------------------------------------------------------------- News is what people want to keep hidden and everything else is publicity. - Bill Moyers _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
