Dealing with input editor conflicts

[jordandouglas]

If there are multiple input editors which apply to the same class, it is not clear how beauti will resolve the multiple matches by picking just one input editor.

For example, the TypeTraitSetInputEditor used by both MASCOT and MultiTypeTree may differ, and they both edit the TraitSet class. If one has both packages installed, its not clear which version of the editor will be used and which will be ignored.

Could there be a way of specifying in the xml file which input editor beauti shoud load?

[rbouckaert]

An InputEditor e declares the type, and any BEASTInterfaceo matching the type will use the InputEditor.
Matching types is done by checking the class of the object o equals that of e.
If no editor has class of o declared, a match is sought with the super-class of o till a match is found.

For example, TypeTraitSetInputEditor returns TraitSet as type, and in MASCOT mascot.util.InitializedTraitSet derives from TraitSet. There is no input editor for InitializedTraitSet, but there is for its super class, namely TypeTraitSetInputEditor, so that is the input editor that should be returned by the InputEditorFactory.

If you need a different editor for the same class X, a workaround is to derive from that class Y extends X and specify an input editor for Y with different behaviour than the input editor for X.