I think section 10.3 of the manual describes what you're trying to do.  You'll need to attach the inspector to its own display.

Personally, when I have an overabundance of model-level parameters, I prefer to used a TabbedInspector to organize them by category under the "model" tab (see section 10.6.4).  I connect each sub-tab to its own inner class inside my global parameters object (I like separating parameters from my SimState, but that's a separate discussion).  That way everything is still in one place (both code-wise and GUI-wise), but not as overwhelming.


On Mon, Jul 14, 2014 at 12:06 PM, Simone Gabbriellini <[log in to unmask]> wrote:

I need to display many parameters that affect my model. Some of them are in the Model tab, but since there are many more (less important), I think that a custom property inspector could be a good way to let the user know about them.

As far as I understand from page 228 of the MASON library, I should produce an inspector for the fields that I need to display out of my SimState class... I think that this code should be the right baseline to proceed but I don't know how to link that to my model:

public class FlagInspector extends PropertyInspector{

    public FlagInspector(Properties properties, int index, Frame parent, GUIState simulation) {
        super(properties, index, parent, simulation);

    public void updateInspector() {
        // do stuff here

where should I call this class in the SimState logic? Is there some example out there I can refer to?


Simone Gabbriellini, PhD

Post-doctoral Researcher
ANR founded research project "DIFFCERAM"
GEMASS, CNRS & Paris-Sorbonne.

mobile: +39 340 39 75 626
email: [log in to unmask]


Ph.D student in Computer Science
George Mason University