taps | simple database import/export app

TabBarController’s delegate does not have to be either of the view controllers. It could be some other object (not even a view controller) that could hold weak references to both view controllers, for example, or post a notification etc

@Jason and @Divyesh have good suggestions. Also the gesture recognizer Tapped handler can be unique to the column and can pass a CommandParameter that I can bind to a value that uniquely identifies the row.

Thanks! Will use some combination of these approaches.

If you want to add all uid under "postLike" collection that is impossible .because You can't store field(uid) in collection(postLike). you can only store field under document.but if you want you can store all uid under "postId" document.

so when user double tap on like, add document "addLike" as you mentioned in your question. when another user double tap on like update document under "postLikes".so that you can keep all uid under one document.

The problem with the above code on first line. I mean declaring myView. Use private lazy var myView: UIView = { ... } instead of using private let myView: UIView = { ... } will resolve the problem.

I've faced this problem, so I think others might face the same. So I post this. Thanks.

Wrap the whole body of Scaffold with GestureDetector and make your operations on the on tap method. and add behavior: HitTestBehavior.opaque, to the gesture detector.

First, let's clear up a misconception. The view model is not where you "make action." The view model is where you want logic. There should not be any relays, subjects or observers in your view model. It should be Observables in, Observables out.

Second, when defining an Observable chain, much like when you are defining a formula in a cell of an Excel spreadsheet, the final result, the thing you want to ultimately do, is the most important part but that is the one thing you haven't described. I doubt that all you want to do is print something.

Third, a Subscription, just like a use-case, consists of a Cause and Effect, with Logic transforming the cause into an effect. The Logic is what goes in the view model, an here the only logic you have described is that "tap" should be the output every time the button is tapped.

So as it stands, the entire use-case you have described is "when the user taps the button, the system should print 'tap'." With only that to go on, we have a Cause (the button tap), the Logic (the word "tap" once per tap) and the Effect (print something.) Which would be modeled like this:

As long as you are adding the UITableView as a subview to the SearchBar or UINavigationBar, you will keep finding these touch issues.

A possible way to handle this would be have an empty container UIView instance at the call site (ViewController in your case) and ask SuggestionsSearchBar to add it's tableView inside that container.

You could use the Raise/LowerChild of Grid to achieve this effect.

I found a couple of solutions to this problem. It boiled down to my ISP provider (Virgin UK) who was bottlenecking the install, probably because of a security issue or bug.

A solution that worked for me was removing the initial failed installation and using a VPN to changing my connection and install it that way.

A second solution would be turning off Child Safe with your ISP.

These are the solutions I came across, the first one worked for me, and I have been told that the second one works too!