I certainly can if you like.  I left it out this sprint because you didn't include it in your initial request and we had that "side track" discussion about what you wanted this sprint.  But, yes, it is a good way to hierarchically organize modifiers.

Think you can see how a UI built to allow someone to construct a symbol from these pieces would benefit from modifier category, as an added way to organize all the options.

--Andy

-:-Sent from my iPhone-:-

On Apr 2, 2014, at 18:38, "Chris Moore" <notifications@github.com<mailto:notifications@github.com>> wrote:


In source/JointMilitarySymbologyLibraryCS/librarian.cs:

> +                                                w.WriteLine(line);
> +                                                w.Flush();
> +                                            }
> +                                        }
> +                                    }
> +                                }
> +                            }
> +                        }
> +                    }
> +                }
> +            }
> +        }
> +
> +        private void _exportModifiers(string path, string symbolSetExpression = "", string expression = "")
> +        {
> +            string modifierHeaders = "SymbolSet,ModifierNumber,Modifier,Code";


Just curious - looks like you are missing "category" also - did you say we need to add this to this csv output?

—
Reply to this email directly or view it on GitHub<https://github.com/Esri/joint-military-symbology-xml/pull/15/files#r11231767>.