I’m in the layout editor working on a screen. Whether I select a screen or component, I can see the context of the table I’m working on: the source is in the pane on the right or in the data pane at the bottom of the screen.
If I click on “Data editor”, I’m not automatically brought to the table/context I was in. I feel like clicking on a little arrow, in either pane on the right or at the bottom, which would bring me directly to the correct table.
Is the arrow there and I’m not seeing it? Any smart workarounds?
And yeah, I feel this sometimes. It would be nice if the system can detect what table the component we’re selecting is for, and then default to it when we open the Data view.
I’m in the layout editor, it knows my context, I wonder if I can navigate to the data editor by keeping the context of the components I’m working on. If I click on “Data editor” at the top, I lose context. Or rather, it brings me to the data source of the screen. It would be nice if we had a way to navigate to the table of the component, thus keeping context?
If I opened two tabs, one with the layout editor and one with the data editor (edit-edit), would that work?
So, I’m finding a solution to my own problem. It requires a few extra clicks and it’s a little prone to a miss-click. But still, it’s a solution.
In the right panel, we do therefore have a way to go from the layout editor to the data editor by keeping context. It would just be nice if that arrow were also right next to the label “Source” (right panel) or right next to the label “Data” in the peek-a-boo view. The arrow is there, it exists.
When in the data editor and returning to the layout editor, if we’re in the flow of things going back and forth, then we land on the correct screen in the layout editor (I believe).
Basically, the behavior stems from the fact that on a given screen, there a potentially many data sources: that of the screen, collections, other components. The context defaults to the source of the screen (in my case the Users table or a Global Settings table), even though I might be working on a collection with a different source.
