hi, sorry to come in again, but the problems get deeper ...
WIN7/64bit PD 0.48.0 (zipped)
i built a lot of patches using [declare] to make sure that any deken-installed externals/libraries are loaded when needed.
up until PD 0.47, the behaviour was like this:
[declare -stdlib GEM]
loaded the Gem library if it was located inside PD's "extra" folder
now (PD 0.48):
PD automatically defaults the deken download folder not to the directory "extra" but to "externals" when the "directories" folder is set (no startup option to change this as far as i know).
but [declare] in PD 0.48 STILL looks inside "extra", unless you define an absolute path to tell it otherwise (which is totally besides the point). as a result, none of these works:
[declare -stdlib GEM] [declare -stdlib externals/GEM] [declare -stdlib ./externals/GEM]
only this does:
[declare -stdlib D:/pd_0.48/externals/GEM]
so, [declare] is therefore not backwards compatible. a bug, IMHO.
possible solutions:
1.) the user must manually change the deken download (externals installation) path back to "extra" again, (but where's the benefit in this ?)
2.) make [declare] search the defined externals/library path (whatever its name is)
since these features are new in PD 0.48, it would be great to at least make them settable with a startup option.
if i may make a wish for pd 0.49:
recursive directory search paths - settable with a PD option ! would ease so much pain ;-)
best
oliver
On 2017-08-21 15:32, oliver wrote:
[declare -stdlib GEM]
Gem is spelled "Gem", not "gem", nor "GEM" nor "gEm", "gEM", "geM", "GeM" or "GEm". you should always aim for correct spelling (Gem won't load on most platforms if you spell it incorrectly).
adsr IOhannes
PS: this probably doesn't fix your underlying problem though
IOhannes m zmoelnig wrote:
On 2017-08-21 15:32, oliver wrote:
[declare -stdlib GEM]
Gem is spelled "Gem", not "gem", nor "GEM" nor "gEm", "gEM", "geM", "GeM" or "GEm". you should always aim for correct spelling (Gem won't load on most platforms if you spell it incorrectly).
yes, sorry for being sloppy on this ...
it's actually working with capital letters on my system, but i know that this is a dangerous habit ...
adsr IOhannes
PS: this probably doesn't fix your underlying problem though
no, it didn't.
changing the "Gem" folder location back to "extra" did.
i really think this [declare] problem should be fixed in the next release, as it breaks many patches and abstractions.
the same error goes obviously for self-declared object names that used to work so far, like
[tof/folderpanel] or [mrpeach/packOSC] etc...
if the corresponding externals are anywhere else but in "extra"
oh, and BTW:
thanks for all your amazing efforts and working weeks to all people involved in the latest PD release, love the new features and improvements so far !
best
oliver
Hi, you can still set deken to download to "extra", so it's not like the new release made this impossible. Thus, it's not like this version introduced a bug, or has something that needs to be fixed.
As I see it, you're just asking for [declare] to have a new feature added, one that would make it easy to search for libs elsewhere other than in the standard path (a.k.a. the "extra" folder) - in the case you are not using (I'll emphasize nothing is stopping you from using "extra").
So, if that's the case, I had already opened an issue and made a suggestion for exactly that! My idea is that the -path flag should also look in the paths that were added in the "path preferences". That would do the trick! Here's the issue report and its relative discussions: https://github.com/pure-data/pure-data/issues/184 (please nevermind the discussion on "additional standard paths", those would other folders that are not the "extra" folder, so it's not something related to what you bring up)
the same error goes obviously for self-declared object names that used to work so far, like
[tof/folderpanel] or [mrpeach/packOSC] etc...
if the corresponding externals are anywhere else but in "extra"
Not at all! If you have any other externals folder set up for you and added to the path, as Pd now suggests (say ~/Pd/externals), any external folder you download to it will allow you to use this slash declaration. So either you're not doing it right, or we have a bug.
cheers
Alexandre Torres Porres wrote:
As I see it, you're just asking for [declare] to have a new feature added, one that would make it easy to search for libs elsewhere other than in the standard path (a.k.a. the "extra" folder)
absolutely right !
are not using (I'll emphasize nothing is stopping you from using "extra").
well, i DO like the idea of a different externals folder to make things a little better organized. so i would love to use it and not having to stuff everything into "extra"
So, if that's the case, I had already opened an issue and made a suggestion for exactly that! My idea is that the -path flag should also look in the paths that were added in the "path preferences". That would do the trick! Here's the issue report and its relative discussions: https://github.com/pure-data/pure-data/issues/184
ahh, great ! so it's already reported. should have looked better !
thanks a lot for your clarifications !
and i will stay with "extra" for the moment
best
oliver