I love the idea of annotations, but stumbled over this issue:
I can make a Group its own parent, seemingly removing it from the cp5 instance and so disappearing from the interface.
myGroup.moveTo(myGroup);
or
myGroup.setGroup(myGroup);
That makes it kind of unconvenient to work with.
Working with annotations for example, I can add all Controllers to a common Tab with
cp5.addControllersFor(this).moveTo(myTab, this);
when I do the same with a Group (which, in my mind, serves the same purpose as a Tab)
cp5.addControllersFor(this).moveTo(myGroup, this);
The Group including all the Controllers vanishes...
I love the idea of annotations, but stumbled over this issue:
I can make a Group its own parent, seemingly removing it from the cp5 instance and so disappearing from the interface.
myGroup.moveTo(myGroup);
ormyGroup.setGroup(myGroup);
That makes it kind of unconvenient to work with. Working with annotations for example, I can add all Controllers to a common Tab with
cp5.addControllersFor(this).moveTo(myTab, this);
when I do the same with a Group (which, in my mind, serves the same purpose as a Tab)
cp5.addControllersFor(this).moveTo(myGroup, this);
The Group including all the Controllers vanishes...