This is a question on an iPad app that I am currently working on. I have a UIViewController with 2 UItableViews. One UItableview will display a list of accounts and based on selections from this list of accounts, we display details on the other UItableview. This has been setup and works perfectly.
Now the new requirement is to have the users swipe the detail UItableview either left or right and the details view should display the details from list of accounts basically as if somebody touched the next row in the list accounts tableview. I have setup 2 swipegestures
for handling this - one for right gesture and another one for the left gesture. This is where I am stuck as I am unable to determine or pass the indexpath of the next row or section from the list accounts tableview.
Any ideas on how to go about doing this?
The UIVIewController knows about the two views. So it can query the master view for the selection. And it can tell the master view to change that selection.
But the detail view can't know about the master view. And it can't know about it's controller. So you use the data-source approach for the detail view to get the selection from the controller. And the delegate approach for the detail view to inform the controller when the user has swiped to another account page.
Related
I'm new to using Microsoft Access, and I'm having trouble restricting a report's output to only the single row I'm interested in.
My organization has a relatively small client list, where a little of their information is used frequently (like their name and account status), and much is used infrequently but still important (like home phone and incident reports).
The way I want to display this information is to have a form that shows a list of our active clients with their most common information, and then has a "Details" button at the end of the client info for when people need to see the rest of that client's information.
So far, I've successfully made a form that links to an "ActiveClients_rpt" report that shows the most common info, and I've made another form that links to a "ClientDetails_rpt" report that shows all the detailed info. My problem is that when I try to restrict the results in the Client Details report by the user input in the Active Clients form, either I have to use a very unaesthetic option (like an ugly combo box that replicates the list of names the user can already see), or (if I try to do something like add a button inside a report) the form sends me the information of every client's detailed info, when I only want the info of the one client.
Is there some way I can use a report (or some other option) to tell Access to only pull information from the row in a list the button is located on? I've tried doing things like making an embedded macro using the OpenForm command to open my ClientDetails_form form with [Forms]![ClientDetails_form]![ID] or [Forms]![ClientDetails_form]![ID]=[Me].[ID] as a Where Condition (where ID is the client's ID #), but everything I've tried has either resulted in an error or not restricted the report like I want it to.
This is pretty complicated without seeing your actual database, but I did a video on something similar that might help here https://youtu.be/nNUjmH72OfI. You basically set a click event in the 'Event' tab of the Properties window while your 'Detail' button is selected (in form design view). You click on the builder button (button with three dots) and either use the Macro Builder or the Code Builder to type out the VBA. The Macro Builder is the simplest way in this case.
That's pretty vague, I admit. But hopefully the video helps.
Problem Statement
We need to create a Drill Down Workflow of screens in PowerApp Portal application where the user can drill down from Parent List to it's child list and so on.
For Example:
-The First screen should list the Phone Brands.
-On clicking any brand->it should bring up a list of Phone Models of that Brand.
-On clicking any phone model, it should bring up the hardware configuration of that phone.
Query:
We have been able add Lists to Child Pages and navigate between pages using the Target type attributes of a List but, we haven't been able to pass the Filter condition from parent screen to child screen
i.e. when the user cliks to drill down from Brands to Models screen.
This results in the Models screen showing Phone models from all brands.
It it simple to achieve the same using PowerApp Canvas application but, we are struggling to achieve the same using Power Apps Portal application.
>>Would appreciate inputs to achieve the same using Power App POrtal Application
you can try to add some query parameter when someone clicks on a brand name in the parent page on the portal and when the user is taken to the child page (model level), there you can read the query parameter to filter.
For readingg query paramter in liquid - https://community.adxstudio.com/products/adxstudio-portals/documentation/configuration-guide/liquid-templates/objects/request/
For adding query parameter on brand click- basic js/jquery should be ok.
I know this question is possibly duplicate however I didn't understand their answers, so I am asking it.
I have a search page and a view page for Customer Details.
In search page if I enter name then I get list of matching customer names.
Now I want to create a link or a button that if I click on it then I should be able to view all the details of that customer such as customer History and everything.
I have both the Search and View Page ready.
My question is how do I create a navigation that if I click on a particular user it will take me to View page and display all the Information related to that Customer
Some time ago, I blogged on how to pass data using the router:
https://yakovfain.com/2015/11/11/angular-2-passing-data-to-routes/
The use case that you're trying to implement looks to me like a master-detail view (list of customers is "master" and the customer details view is "detail"). I wrote another blog on this particular scenario:
https://yakovfain.com/2016/11/20/angular-2-implementing-master-detail-using-router/
You could use a localstorage to solve it. It's so easy to do and works like a BD Key->Value on front-end.
I'm very new to NgRx and am trying to wrap my head around it. I understand the objective is to have a data store where different types of state reside. I'm trying to understand how to work with lists of data.
Scenario 1:
user first navigates to a list in which case an effect fires to retrieve list from backend/API. On success, the list is saved to the store and the UI component responds to the observable via | async and renders the list. The user clicks on an item to view the detail. We can either store the selected item's Id in the store then simply use a filter mechanism to retrieve the detail data from the list array in the store. Or, we can make another effect call to server for detail payload. I'm assuming the decision point here is if the list contains all of the data needed for the details page?
Scenario 2: assuming the list in the store contains all of the data required for the detail page and user clicking on an item in the list simply saves the selected item's id to the store then navigates to the detail page where the detail data is simply filtered from the list based on the selected item id in the store, what happens when the user refreshes the browser URL on the detail page? When this happens, the list is no longer in the store and neither is the selected item's id. However, the selected item's id is in the URL and route. How do you handle this scenario? Do you rebuild the list in order to retrieve the detail record?
Scenario 3: what's the best approach for handling a scenario where you have different subsets of data from the entire list. Perhaps you need to see a list of items that are 'pending' and another list of items that have been created this week, etc. It seems very inefficient to download all records into the store as the master list then simply filter out the ones needed for different views. I've read tutorials where you have the master list in store then simply have Ids in another part of the store that make up the different slices. This seems very heavy and a duplication of the database onto the client. What is the best approach for having filtered lists within a store?
Thanks for your help and insight.
Scenario 1: You're spot on!
Scenario 2: It depends.
you can store the data in localStorage for example
the list has to be fetched via the backend API
Scenario 3: keeping your state normalized is key here (you'll work with IDs). Also we don't have to load all entities at once, this can be done partially. The redux docs has a performance section that you can read.
One "Search" button is there in the JSP page. After taking all values for searching, the form is submitting.
In processAction(), I am getting all parameters. Using these parameters, in doView() I am consuming one API (JSON data). Creating one JSON object for input to the API and consuming it. Now I got the output JSON data and have passed it to the jsp using renderRequest.setAttribute("jsonString", json.toString());
Then showing search result using this jsonString.
Its working properly.
The issue is, its not creating multiple instances for multiple users. If one user done a search action, the same search result will show to each user if they refresh the page.
Why each user not having separate instances?
Now all users of this page can't do search action as they wish. If one user does, the same result will be shown to all. How can I fix it?
Why session of a particular user is sharing to all? Or What is the actual reason of this issue?