@Cycling74 staff: [markup] object
Dec 18 2018 | 1:07 am
By browsing the the MC help files I discovered an object called [markup] that is obviously one of those created for internal/staff purposes. (And discovered that is was already available in Max 7!!) It seems to be very useful for documentation of projects, especially as HREFs in links can be used to send messages to Max. Would it be possible to get further information? Especially regarding the define_element and undefine_element messages?
- Jan 31 2019 | 11:26 pm+1
- Oct 10 2021 | 11:37 am+1
- Oct 12 2021 | 1:45 pmI have put a small unofficial help file here One reason it's not shared by c74 maybe the problems whith the underline attribute. They should really put some effort into this and make it a public object. I only tested on Win. If you notice differences on MacOs please report back.
- Oct 12 2021 | 2:17 pmThis is great! Thank you so much @11OLSEN!
- Oct 12 2021 | 3:02 pm@11OLSEN you are very kind. This will be now my markup default help patch :) Thank you.
- Oct 12 2021 | 3:24 pmsry if not close enough releated: how can you make your abstractions collection print something to the console at max start? not externals, just patches (which arent loaded, so one must use something else)
- Oct 12 2021 | 4:08 pmYou mean like the way bach always prints to the console everytime I open max, regardless of whether i am using the bach objects or not? ;) (yeah I don't see the connection with op, lol)
- Oct 13 2021 | 2:45 amyes that. just on max start.
- Oct 13 2021 | 8:02 amUnfortunately, I think that happens because they have the bach external under the "extensions" package folder. Maybe someone else can explain it better, but it seems that it forces the externals inside that folder to be loaded on max start. Then, it a matter of... well, making your external in such a way that it prints to the console the first time it is loaded. ... and if you want to place a patch in there with a loadmess you can do that too! But it seems that a patch is actually opened (and will stay open :/ ). So, you might need to do something like this:Hope that helps :)P.S. do you have a new abstraction collection coming out? Would love to check it out
- Oct 13 2021 | 10:02 ami´ve never tried this but it sounds logical that patches would have to open on launch just as compiled objects. :) (but how would you do it for patches?) yes, that could still be a solution which does not hurt too much, i already use patches to re-enable a "forgotten" menubar which also closes itself after doing its job - you hardly see it even on slower computers - and my nato helpfileslauncherhelperpatch also works that way. that printing thing would be nice for checking which version of a package or project is installed. (i.e. first of all on my own computers) oh, i have yet to reupload the 2012 collection to somewhere, thanks for the reminder.
- Oct 13 2021 | 1:19 pm+ 10.
- Oct 13 2021 | 1:50 pmwith apologies to @Jan@Roman
i´ve never tried this but it sounds logical that patches would have to open on launch just as compiled objects. :) (but how would you do it for patches?)Just create an extensions folder inside your package folder, and drop the patch with the loadmess in there.
oh, i have yet to reupload the 2012 collection to somewhere, thanks for the reminder.Please do. And keep me in the loop ;)