Why only one sender substring? about klaxon HOT 8 CLOSED

[deleted comment]

It would be great if this could be fixed. Right now Klaxon is not 100% 
foolproof for
me beacause of this.

This is also an issue for me as I get SMS messages from several sources.. not 
all 
that I want to be alerted by in this way.  Allowing for multiple search strings 
would be great feature and would complete this application for me. 

I too would like this as our office pages us using 3 email addresses

My current contract uses Hiplink which uses a different sender string for each 
page. Wildcards in the search string would be a great help. For multiple search 
strings, it would also help if you could designate different alarms for each 
pattern.

My office pages me from a set of 5 different numbers. I've stored all 5 numbers 
under a single contact and it would be great if there was a way to make klaxxon 
go off only for this contact. I don't set klaxxon to consume the sms messages, 
so this way makes it easier for me to look up pages from Messages.app

Allowing the user to mark any messages from a contact as being a page would be 
a really nice way of handling multiple different numbers (that don't 
necessarily share a common prefix)

Ok, apologies for how long this has taken, but v.26 (which will appear in the 
market in the next day or so) has a fix for this. The fix allows multiple 
sender strings, separated by commas.

Integrating this matching with Contacts is proving to be a huge hassle, so i 
have implemented this fix instead.

As for the person who asked about wildcards, the matching uses 
String.contains(), so any part of the sender's phone number or email should 
work just fine, no wildcard needed.

--m.