Community
Participate
Working Groups
The new mechanism to jump somewhere and jumpBack works but sometimes not as easy as it should be. You can jump to a submodule and then jump back. However if you jump to a module, then in the configureRidgets method of the SubModuleController several things dont work. - isJumpTarget() is false..... (workaround is to use getParent().isJumpTarget()) - jumpBack() does not work (workaround is to use getParent().jumpBack()) I think it would be better if the target does not need to know whether to source jump to the submodule or to the module or modulegroup. It should also work if you jump to a submodule that is not selectable (a grouping node).
I´m not sure if this should be the general strategy for "jumpBack". At the moment a single node of any kind is the target of a jump. Do I understand you right that you want to inherit the "target state" recursively to all children of the target node and allow overriding the target state of these child nodes if they get directly referenced by a jump? What should happen if a new child is added to the target node. Should the new child be in target state? I think this would break the whole jump context from the end users perspective. I think we first have to clarify those special cases before we start implementing such a general stategey. Perhaps we could define a special behaviour for the case when the target node has only one child ...
The target state of a Module is now inherited to the direct child submodules.
