The navigation between components is very inconvenient when working with a high number of inner components. It’s not uncommon for us to go between 5 and 10 levels deep, especially for our data apps.
As such, I often need to troubleshoot an issue inside an inner component, go back to higher components and run those to see if the problem was solved. In the new UI, I always need to re-open all the components since they are sequentially linked. That is extremely annoying to develop workflows.
In this example, I’m at level 8 but can only see levels 1 through 5 and a part of 6.
If I want to go to level 7, I first need to go to 6 and then open it again. If I want to run the entire workflow and again need to work on level 8, I’m forced to open them all again.
Moreover, whenever the number of nested levels goes up, some of the UI element disappear or are blocking the view. The mode selection and zoom level has disappeared. Only whenever I move back to level 5, it appears again.
Steps to reproduce:
Open a workflow
Open a component with a high number of inner components
Try to easily navigate between the different components
Actual results:
Having to open all components again when working from the highest to the lowest level.
Expected results:
Have independant tabsheets again to quickly switch between components.
@k10shetty1 We’ve just made the upgrade (from 4.7.8) to 5.4.4 and I’ve noticed the same behaviour in components as described here by @ArjenEX way back.
Is it possible to share info on these tickets NTX-2244 and NTX-2245 (because the tickets on their own don’t solve anything)?
The issue with the breadcrumb (NXT-2245) has been resolved, it is now scrollable, and the right-hand side items (zoom and cursor modes) remain visible even with many or long levels.
The other ticket (NXT-2244) is still open, and there isn’t much of an update at this point. Once there’s a progress to share, we’ll update this thread.
Hi @k10shetty1 ,
Thanks for the info. Unfortunately (for me) NTX-2244 is not solved. During developments I used to have opened different components which were not inner components of each other, but through data ‘communicating’ with one another. I guess the flip-flopping between open tabs has to be changed into closing and opening from now on (the Ctrl-Alt-Enter is already memorised by me ).
Best,
Jan
).