First, I apologize if my English is not very good, I am writing this query with the help of Google Translate because I do not speak English perfectly... and here is the query where I will try to explain it as simply as possible since I have been around 6 months driving ignition and studying on my own but I still consider myself a beginner in this world...
I am looking for an easy and practical way to navigate between a main screen (I have called it overview) that contains different Embedded in which if we select one it directs us to a second view in which we will obtain different variables or information from the one we select...
Overview with two embedded
The second view is made up of different embedded but we will only focus on the upper left part
Secondary View, if we selected 'Velocidad' for example
My intention is that when a different embedded is selected in the 'overview' it brings me all the information, labels or variables that correspond to that embedding that was selected (What is seen in the secondary view)... I am using navigation events in the embedded of the overview to move me to the second view but as you know I can't get that information to change.
As you can see, I created these parameters for the second view that have to do with the content of this view
There have to be 9 sets of parameters for the nine spaces you see in the second view but I have decided to start with two
and
These are the embedded parameters that we are interested in changing in the second view
I'm not sure I fully understand what you're asking, but if you want to navigate between different embedded views you can set up a view param and configure the page URL to include said view param.
An example would be /overview/nombre-variable/:varNum;
The varNum would be your view param which you would define previously and cycle through all of your variables using that. You would also have to set the correct target of your embedded views to match which variable you're trying to open.
As far as the information, labels and variables you've mentioned, you can set up a popup view that shows the details that you want to show using an instance param which would be linked to your view param.
1 Like
Ok I'll try to explain what I want to do with more specific images...
This is my overview in which there are different embedded, if I select one...
In this case I select 'velocidad' and it takes me to a second screen that we will call 'Details view'
As you can see, if I select a different variable (Embedded), it takes me to the second view (Details View) and contains information regarding the embedded that was previously selected. This is exactly what I'm looking for but I would like to find a better and more practical way to do it, since for now I have only done it with other views which fills the project with many views and we don't want that.
Here we can see again the second view (details view) that comes from another embedded of the overview, in this case we are seeing the details of the embedded of 'Cuba Level'
Different information, same template or view...
Well if you're trying to navigate to a different embedded view by clicking on different embedded variables, you can use an onClick() action handler and use the system.perspective.navigate function. If you want a separate view to display your information you can set up a dedicated popup view that opens the page you configured using the aforementioned instance param.
As far as I know, navigating between different views using view params is the most effective way of doing so. It's also good practice to organize your views in adequately named folders and subfolders. Be careful your view path is listed correctly in your embedded view target destinations.
Could you post more screenshots of the current view params you have set up as well as your embedded view configurations?
Well here I leave you a screenshot of how I have distributed the project
I hope you are referring to this, if not let me know and I will find more screenshots.
@Jose_Lopez, tips for forum Markdown syntax:
Use the ” button or > for quotations and the </> button for code as show here: Wiki - how to post code on this forum.
Yes, that what I wanted to see. From your onClick action handler configuration there are no instance params configured. Take a look at this rough example I created:
I'm using a tab container to cycle through all of my tabs (A, B & C). The tab container is embedded in a popup view which has a view param defined called viewParam. The tab container has a defined property binding to said view param:
On my Overview I created a view param called varNum which cycles through all of my tabs by calling an instance of viewParam in the popup view configuration:
And here's the instance being called:
This is a dummy example of what I understood you were asking for, you can apply this logic for your embedded view navigation.
1 Like
