Just starting - a few questions


#1

I just received my first AxoCore and started to dive into custom objects right away. I struggle with very simple things but the web and forum search doesn't bring up a lot of info. So... here are some questions:

  1. I'm trying to create an object that has a buffer of configurable size. I figured, an attribute might be the right thing to use for the buffersize. Looking at other objects, I see that they use "attr_xyz" in the code, but once it's compiled, that is replaced with the actual value. I also see attributes used in preprocessor statements, so my assumption is that attributes are like a pre-preprocessor, right?
    When I add an attribute "buffsize" (min: 1, max: 100) and add this line into my objects local data section int16_t delayline[attr_buffsize]; I get an error saying xpatch.cpp:43:16: error: 'attr_buffsize' was not declared in this scope. So, why is my attribute not replaced with its corresponding value?
  2. I created my object as a object/object in a blank patch. How can I save it to my library? The XML-tab doesn't update, so I can't just copy that. I can copy it from the *.axp file, but is that the preferred way?
  3. What do I choose for the uuid of a new object?
  4. Is there a difference between datatypes like frac32.bipolar and frac32 apart from the different logo in the patcher?

Sorry for those dumb questions... I really didn't find answers via the forum search...


#2
  1. your doing the right thing, not quite sure what your doing wrong... you'll need to post the object. (see 2.)

  2. when editing the object, choose file, copy object to library

  3. (2) will do this automatically for you, you dont need to edit the xml at all
  4. no difference, its just to allow users of the object to know what to expect.

#3

thetechnobear, thank you for your answers. Apparently, re-opening the patch solved all issues for me.

  1. Somehow the GUI wasn't consistent. After reopening, the attribute was still named a1, while it definitely said buffsize before. I also noticed that pressing the add button on the displays page didn't seem to do anything. Now, after I re-opened the patch, I can see several entries in the list that didn't show up before re-opening. Looks like there are some issues with the gui.
  2. Thanks, I tried right-clicking the object but I didn't try the file menu. Thanks! BTW: After re-opening the patch, the XML tab shows the updated data now.

#4

On macOS you don't need to close the editor, but do need to move off the field for the change to register

(Might be different on Windows /Linux)

The xml view is largely irrelevant these days.
It's not meant to live update