i have a little headache here
1. as of late (4.6), i have some abstractions that will report the
old "no such object" error,
unless they are instantiated with the ".pat" as a part of their name.
i.e. i have an abstraction saved as a file on disk called "myabs.pat".
if i make a max object "myabs": no such object
if i make a max object "myabs.pat": no problem
this does not happen with all abstractions;
i only have a couple that post this problem but i can't figure out
what's special about them.
they are binary files.
2. i've now seen two instances of externals compiled for UB
compatibility that give the
no such object
error, even when they are in the search path.
luke and i tried to debug what was going on with 5/6/7 attempts of
various compiler settings (he had just tried porting percolate for UB)
what i find is:
-if the .mxo is in the search path, it is not found
-if it's in the max support folder, it is not found
-if i drag the mxo onto the max application, then try to open it's
helpfil, it IS found!
-then i quit and restart max and it is no longer found (eventhough
it's still in the search path).
anyone else seeing this?