so when im on Tab 2, i click next arrow it should show then, info from the second row of table that is on tab1, so user wont need to go back to the tab1 at all
so for now i can have table hidden in second tab, but that will add more resources to that tab, maybe will got slow? client wants that basically as they are using access right now
instead of working with the table rows you can work with the data source and set a transformer to select the data depending of a variable containing the index.
now with your buttons you increase/decrease the variable and the transformer will responde to the changes
Any interaction with a table directly in another container view can't be performed, to my knowledge. This includes actions such as selecting a row, unselecting a row, clearing selections, etc.
thats the thing, user wont want to click anything only the next and prev buttons. Maybe something to always have index 0 always got the first row? of course after each refresh of app it will go back to index 0