Eric Lyon

There seems to be a conflict between these two macros, at least if I'm correctly understanding their intended behavior. Say that I have four attributes for an external called oscil~, whose order I specify as follows:

    CLASS_ATTR_ORDER(c, "frequency", 0, "1");

    CLASS_ATTR_ORDER(c, "waveform", 0, "2");

    CLASS_ATTR_ORDER(c, "xfade", 0, "3");

    CLASS_ATTR_ORDER(c, "amplitudes", 0, "4");

In the inspector under the oscil~ tab, the attributes are listed in the order requested. Now I add a single additional category and assign just one of my attributes.

CLASS_ATTR_CATEGORY(c, "amplitudes", 0, "Waveform");

The new category is created correctly and the "amplitudes" attribute is assigned to it. However in the oscil~ tab, the "amplitudes" attribute now appears first, even though it has been assigned order 4.

	CLASS_ATTR_ORDER(c, "frequency",    0, "1");
	CLASS_ATTR_ORDER(c, "waveform",  0, "2");
	CLASS_ATTR_ORDER(c, "xfade", 0, "3");
	CLASS_ATTR_ORDER(c, "amplitudes", 0, "4");

conflict between CLASS_ATTR_ORDER and CLASS_ATTR_CATEGORY