Max complete Object and attribute list
Hi,
every now and then I receive a hint by someone for an object attribute that is not mentioned in the objects help file. Is there any complete list of Max objects and ALL their attributes?
Sorry, if I am number 10542 to ask this....
Only object I know with many undocumented messages is thispatcher(I think we should make a thread to collect them all with the community). You found hidden stuff with other objects as well?
The thing about undocumented messages is that said lack of documentation may certainly be an oversight, but I would counsel y'all to keep in mind that said messages may be deprecated or removed at any time. Relying on them might not be a good long-term strategy.
Yes, I was told the same by tech support a few months ago with respect to using (;max launchbrowser) to launch applications in Windows. It works, but only does so because Windows allows you to type file names into browser address boxes. However, it was not the original purpose for this message and is not in the documentation because it will stop working if Microsoft ever took this capability out of their browsers.
Hi all,
thanks for your interest and responses.
@11Olsen: I think you are pretty right that it was only thispatcher, but still, the "locked"-message for example is good to know
@Gregory Taylor: I totally understand your issue. There is a package called JAMOMA, and that package has some nice objects. But obviously since 2016 nobody ever spent a minute on it, the objects are unusable with Apple's silicon comps, because they are not updated. I asked cycling to either take the package down or at least publish a warning
@Andy Maskell: although I do not know these Windows specifics, I think that objects and their attributes – specifically if they come directly from cycling74 – should be valuable at all time and if an upgrade is necessary, these objects should be upgraded. How else can you ever use them?
Thanks for your interest
All the best
@Ullstein - I think what tech support were trying to say is that a command such as (;max launchbrowser) was developed for a specific purpose and it works for that purpose with all OS versions. If that command needed an update to continue doing that task then it would be beholden on Cycling '74 to update it. If, however, other ways of using the command, such as launching an application, are possible because of unexpected bonuses presented by a given version of a given OS, then Cycling '74 can't be expected to chase after all these spurious exceptions.
@11Olsen - Are you going to start the thread then as you probably have plenty of ideas already? I've been wrestling with [thispatcher] over the past month or so and I bet there is a "hidden" command available that would have helped me!
@Andy Maskell: of course. but I am not talking about "abusing" objects. Still I think Objects need to keep their functionality over the years, at least not go below it.
I guess you agree
All the best
@Andy Yes I will open up the thread when i'm home.
BTW: I have an external prototype here that is like an extended [thispatcher]. That could have solve your last 2 problems (a second view of a bpatcher, minimize a window). Still work in progress and maybe not completely ready to be released. If you contact me I'm happy to share it in it's current state. I hope that this external will eventually make it unnecessary to use undocumented features of [thispatcher].
@Ullstein - Yes, I agree entirely.
@11Olsen - Superb. I'd love to see that when it's working.