Preferred way to build a model programmatically these days? about lx

[mcslee]

If you want to build your model statically in code, keep extending LXModel like before and ignore all the LXStructure and LXFixture stuff. Those fixtures are things that would show up in the dynamic model construction system (e.g. not via JSON file, but still via dynamically adding/removing/modifying fixture settings in the left-hand model pane).

If you pass in a LXModel instance at constructor-time, all that stuff is ignored and your static model will be used instead. So, basically - make no changes if you prefer to stick with how it worked before.

[Geethree]

Though, leveraging the new LXStructure and LXFigure construcuts would allow for using the UI to tweak things and save it to the project?

[mcslee]

Yep - if you want to go that route, you can define your own custom LXFixture subclasses and register them. Don't pass an LXModel to the LX constructor. Your custom LXFixture type will be available to add in the left-hand Model column as a fixture type.

You probably want to subclass from LXBasicFixture if you're using a normal protocol type (e.g. artnet/sacn). That'll automatically get you the basics. Take a look at StripFixture to understand the basics of what your subclass needs to implement. It's mainly the methods: size() which indicates how many LEDs are in the fixture, and computePointGeometry() which sets the positions of the points based upon fixture geometry.

Feel free to ping w/ questions if it's not clear or working as expected.

[raldi]

It's not the prettiest code, but if you'd like a working, recent example to read over: https://github.com/titanicsend/LXStudio-TE/blob/main/src/main/java/titanicsend/model/TEWholeModel.java