Thanks to multi-targeted yak packages, we will soon release the ShapeDiver plugin compiled with .NET 7 as well as Framework 4.8. So far, the testing is going well, except for a small issue.
So far, we have been using a somewhat hacky way to order the sub-categories of the plugin: as far as we can see, they can only be ordered alphabetically, and we have been using zero-width space characters to control this order, as such:
public static class SubCategoryNames
{
public const String INPUTS = "\u200B\u200B\u200B\u200B\u200B\u200B\u200B\u200B\u200B\u200B\u200BInputs";
public const String OUTPUTS = "\u200B\u200B\u200B\u200B\u200B\u200B\u200B\u200B\u200B\u200BOutputs";
public const String DISPLAY = "\u200B\u200B\u200B\u200B\u200B\u200B\u200B\u200B\u200BDisplay";
public const String TEXTURES = "\u200B\u200B\u200B\u200B\u200B\u200B\u200B\u200BTextures";
public const String IMAGES = "\u200B\u200B\u200B\u200B\u200B\u200B\u200BImages";
public const String JSON = "\u200B\u200B\u200B\u200B\u200B\u200BJSON";
public const String ANIMATION = "\u200B\u200B\u200B\u200BAnimations";
public const String SHAPEWAYS = "\u200B\u200B\u200BShapeways";
public const String EXTRA = "\u200B\u200BExtra";
public const String APPBUILDER = "\u200BApp Builder";
}
This still works fine in .NET Framework but the .NET 7 version seems to ignore the zero-width spaces, which messes up the order of categories as we defined them.
Is there a better way to order sub-categories? If not, could this issue be looked at?