Was wondering how custom objects work with the embedded patcher object thingy. Can they only be used in that specific object or can they be used in other patches as well? Or is old way of using custom objects(copying them to Axoloti search path) preferred if youd like to use them across more patches?
Guess I need to install it and check out how it actually works. I haven not installed the new version yet. I only have a "half working" board atm, so I wait a little bit before testing it out.
Sorry cut paste error , I've corrected.
Home folder is the one axoloti.prefs is located in
We use that folder (by default) for anything writable.
You can of course use other folders, see video I did on this
Embedded means in a patch , so only useable in that patch (that's kind of the point 
)...of course can be cut n pasted into others.
The point of embedded sub patches and objects , is to avoid lots of patch specific functionality cluttering up the file system.
I now use embedded stuff as the 'norm', and only save it out as an axs/axo if it's really necessary!
Yeah, guess I need to try it 
Cant wait, though its gonna be a while. Had planned to send boards in monday, but I couldnt and cant send them before next monday.
am i doing something wrong that i dont see and add/remove/edit library button? im using Windows but probably should install this on my macbook....
is it allowed for us to upload our contributions directly to github or are you going to pull from the forums and update the git yourself?
as in the post... grab yourself a github account, and post here, then you will be able to sync (push) directly to the community library.
(see https://youtu.be/BbwRlavGSQw)
wow!
the object editor is amazing now!
one thing i noticed, some options in the 'parameters' -section appear to be broken,
i.e. mess up the GUI of the object entirely...
(everything with 'Int 32')
I Actually did my first few lines in c++ today...
I am a bit vague about a lot of basic concepts, whats a
'uInt32u' compared to a regular 'int' , for example ?
are there any ressources you could recommend , any documentation?
will fix that
you probably mean uint32_t?
int is not guaranteed to be 32 bits, depending on the compiler and target architecture, while int32_t is always 32 bit.
uint32_t is the unsigned version of int32_t.
can I please make a request , I need more testing on the contributing side of the community library.
you will need to go through the setup steps for contributing, as outlined in the community library section on the forum,
once done, can I ask user please contribute a test object to the library,
it doesnt matter what it does, or doesnt do..
and then report here once you have done it, with success/issues.
and the object name, I will then delete it.
note: we have found a small issue with 1.0.7 and windows for contributions, so please wait for a new version of a test release. (hopefully very soon )
just booted up 1.0.7 on my OSX 10.11.2 and, once I updated my libraries, received the following error
Please all users of 1.0.7 upgrade to 1.0.8...
and pay particular attention to the post Ive made in the 1.0.8 thread. here
this step will be need even if you skipped 1.0.8 and when to the next official release, so best to do now
