I change the position of textfield like this:

RAMReel(frame: CGRect(origin: CGPoint(x: 0, y: 100), size: CGSize(width: self.view.bounds.width, height: 100.0)), dataSource: dataSource, placeholder: "Start by typing…")

but when typing... the position goes to bottom...

I love this component, sleek and works awesome; but there is something I don't think is working. In the gif, the user can scroll the collection and tap the textField, so the option shown behind it is selected. It seems at the moment this is not working, so there is no easy way to select the option shown behind the textfield. Furthermore, when I tap done in the keyboard, I only get the textField content; whereas I would expect to get the option that is being "suggested". Is there anyway this functionality might be included again? Or maybe I'm missing the point of the component ;p

I can't seem to figure out how to do case-insensitive input matching. By this, I mean I would like a input of "michael" to show all possible inputs like "Michael". This doesn't have to be added now. I'd at least like to know where is best to make that change.

I've been trying to get this plugin in, as well as your one here: https://github.com/Ramotion/animated-tab-bar

I'm running on Xcode 9.4.1, using Swift 4.1 for my project, and using IOS 11.4. I tried to pull your project here and I get a bunch of compile errors when I try to build the project. I can put screencaps of the errors I'm getting if necessary. Any help is greatly appreciated!

Some critical closure retain-cycle causing memory leak issues were fixed where scrollDelegate and textFieldTarget capture closure making strong reference.

To give background story a little in advance, I am using my own customization based on reel-search for application that will be released V1.0 soon :) (named : 'All Dayz') Thank you for the awesome repository and I am very glad to try pull request to this.

To explain the pull request, I fixed some critical memory leak issues caused by closure memory retain cycle. It can be very easily reproduced if instead of existing sample example using Single ViewController, we use root-navigation controller having ViewController1 and push ViewController2 having reel-search and back to VC1. Using navigation controller, if we test push and pop current single ViewController example, memory is not released after pop. for example, it increases more than like 500MB after push and pop 3 times since data.txt is huge data set. That means, this memory leak issue occurs in real project unavoidably except for the case where we only use single VC app having reel-search.

Below is the memory leak cases where I push and pop 3 times current reel-search example.

FYI, Memory leak retain cycles cases are categorized as 2 group as below attached : (1) TextFieldTarget, NotificationCallbackWrapper case

(2) ScrollDelegate case

I resolved these retain cycles and result is below with same test case above.

I hope it helps, Thank you!

so when I type - the keyboard ui blocks self.editingTarget = TextFieldTarget(controlEvents: UIControlEvents.EditingChanged, textField: textField) { if let text = $0.text {

            dispatch_async(dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_BACKGROUND, 0)) {
               dataFlow.transport(text)
            }

2016-05-03 11:33:56.369 RAMReelExample[346:42807] This application is modifying the autolayout engine from a background thread, which can lead to engine corruption and weird crashes. This will cause an exception in a future release. Stack:( 0 CoreFoundation 0x0000000182c5ae50 + 148 1 libobjc.A.dylib 0x00000001822bff80 objc_exception_throw + 56 2 CoreFoundation 0x0000000182c5ad80 + 0 3 Foundation 0x000000018370bafc + 88 4 Foundation 0x000000018370b9c0 + 56 5 Foundation 0x00000001835911ec + 56 6 Foundation 0x000000018358fa44 + 816 7 Foundation 0x000000018358f5cc + 284 8 Foundation 0x000000018358d1c8 + 228 9 UIKit 0x0000000187ea9958 + 468

While not an ideal fix for your react pattern - I've hacked around this by doing searching on background thread. But it's not stable in conjunction with scrolling. https://github.com/johndpope/reel-search/commit/bdc6190411cc0b88cb0b774c2aa65b7d00141ba1

so on closer inspection - you're calling adjustScroll /updateOffset too much

func scrollViewDidEndDecelerating(scrollView: UIScrollView) {
    scrollTo = scrollView.contentOffset.y
    adjustScroll(scrollView)
}

func adjustScroll(notification: NSNotification? = nil) {
    collectionView.contentInset = UIEdgeInsetsZero
    collectionLayout.updateInsets()
    self.updateOffset(notification)
}

which is then calling ->>>>>>

func updateOffset(notification: NSNotification? = nil) {
        self.collectionView.reloadData() // THIS IS EXPENSIVE 
         self.collectionView.layoutIfNeeded()  // THIS IS EXPENSIVE 

You're effectively reloading the tableview every time the user touches the screen.

Sorry, the previous pull request (https://github.com/Ramotion/reel-search/pull/27) did brake selected item functionality. There is no need to scroll, but the selected item still should be set.

I found out I missed something, There is some possibility, which is in theory, these two closure containers may be possible to be deallocated in run-time because of weak var. I think it'd be better that self should be weak rather than closure container variable itself. So, I tried to trim a bit, keeping same execution.

Thanks!

Hello. I have checked your readme page, but did not understand if the following can be implemented with your cute framework.

I want to create TextField with search, just like your framework does. But if user types value that is not presented in searched results, I want to use it. Can this be done by default?

Sorry for stupid question. Have not yet tried to implement it, just looking for possible ways to do this.

RAMReel/Framework/DataFlow.swift:

+precedencegroup ComparisonPrecedence {
+  higherThan: LogicalConjunctionPrecedence
+}

-infix operator *> { precedence 180 }
+infix operator *> : ComparisonPrecedence

RAMReel/Framework/TextFieldReactor.swift:

+precedencegroup ComparisonPrecedence {
+  higherThan: LogicalConjunctionPrecedence
+}

-infix operator <&> { precedence 175 }
+infix operator <&> : ComparisonPrecedence

First: How are those operators became Comparison operators? Second: Comparison operators in Swift 1-2 had precedence 130, defined operators — 180 and 175. 180 > 130 and even 175 > 130. Third: 180 != 175 and 175 != 180. Why in hell they're in same precedence group?

What has to be done:

• [x] Rename defined precedence groups, they're definitely not comparison operators.
• [x] Precedence group of <&> operator has to be higher than Exponentiative (to keep backward compatibility).
• [x] Precedence group of *> operator has to be higher than precedence group of <&>

When using your library with the example it puts the suggestions above, below and in the actual textfield without user interaction.

Is it possible to configure your library to behave as in the demo gif, so that the user first needs to scroll down to fill the textfield with a suggestion?

Thanks

would this be possible to be used with with coreLocation Search. Because i would be searching for the location instead of having them on a list like in the example. if so please guide me down the right direction.

Hello,

I tried to apply theming in the sample project, then Xcode said

'RAMTheme' initializer is inaccessible due to 'fileprivate' protection level

`let textColor: UIColor = .white let listBackgroundColor: UIColor = .blue let font: UIFont = UIFont.systemFont(ofSize: 18)

    ramReel.theme = RAMTheme(textColor: textColor, listBackgroundColor: listBackgroundColor, font: font)`