27 replies to this topic

[David DelMonte]

[quote]@David: 1. When I perform a search, I click search but the keyboard is not released. [/quote]

We've actually left this without a default action and left it for the developer to decide what to do depending on their own desired application behavior. To dismiss the keyboard, just implement the SCTableViewModelDelegate method called "tableViewModelSearchBarSearchButtonclicked:" and call [tableViewModel.searchBar resignFirstResponder].
[/quote]

ok that's fine.

[quote] I am guessing that we could easily make it work with STV if we subclass it into a new SCSearchDisplayController for example. I think UISearchDisplayController provides a lot of really cool visual cues, and if I am right about the subclassing theory, then we should probably have SCSearchDisplayController ready for STV 2.1. How urgent do you need this David?
[/quote]

No rush Tarek, later today would be fine

Seriously, I can live with this until 2.1. (We won't lose our databases (?) - I want to deploy this app soon)

[quote]I wish everyone would chip into these discussions, unless Tarek wishes otherwise.

I would actually LOVE to!! [/quote]

Great!!! Thanks for helping the noob as usual Tarek..

(Whatever happened to COBOL?)

[carl grainger]

Hi all,

I'm just wondering if this behaviour is normal or if I'm screwing things up as usual;

If the searchBar has text, the scopeBar becomes ineffective.

The scopeBar looks and behaves as normal and the delegate method searchBarSelectedScopeButtonIndexDidChange fires BUT the tableView remains as was.

I'm new to scopeBar and not sure if it's OK to use it before during and after using the searchBar. However on seeing this behaviour my first thought was to have the scopeBar disabled when the searchBar has text.

Appreciate your wisdom on this..

Carl

[David DelMonte]

Carl, I'm at the airport. I will check what happens to my app between flights.

David

[Tarek]

Hi Carl,

Thank you very much for reporting this! We have replicated your code and there seems to be a bug with reloadBoundValues ignoring whatever search value is present in the searchBar. We'll fix this in our next release. Thanks again!

[carl grainger]

You're welcome. I wouldn't have guessed it was a bug, but it's great to know you guys are already on the case.
Cheers

[David DelMonte]

Tarek, I should have said thanks before.. Been without the net for a week and just catching up..
I have search and scope working great now.

One more thing

I have a single search term called frontWord. Is it possible to add a second term called "backWord"?

One other more thing

Is it possible to search in non-english languages (greek, arabic, etc)?

David

[Tarek]

Hi David,

You're welcome, never mind at all

I have a single search term called frontWord. Is it possible to add a second term called "backWord"?

If I understand you correctly, "frontWord" and "backWord" are attribute names, right? If so, then yes, just place the attribute names separated by semi-colons in your SCArrayOfObjectsModel property called searchPropertyName. For example:

myArrayOfObjectsModel.searchPropertyName = @"frontWord;backWord";

Is it possible to search in non-english languages (greek, arabic, etc)?

We actually haven't tried this before. Are you having any problems searching with non-latin alphabets?

[David DelMonte]

Thanks Tarek!

tableModel.searchPropertyName = @"frontWord;backWord";

works perfectly.

And, search CAN find a word in a foreign key - well, at least Greek and Russian. I haven't activated Arabic, Hebrew or any Asian languages yet.

David