Blocking Calls from 'Unknown'
ipse:
Quote from: ianobi on August 09, 2014, 05:57:44 am
The problem is the label "Telemarketers" contains reserved characters. In a digit map you can use any combination of 0-9,*,#,+,-,A-Z,a-z, except m, M, s, S, x, X which have special meaning in the digit map syntax.
Hate to harp on this, but the default label "ste" contains a reserved character...is it working because it's a system default (maybe hardcoded and not parsed)?
I am embarrassed to find problems with my digitmaps after 1 year....I admit to using some suggestions from this forum that might not have come from the gurus.
InetUser:
Quote from: ipse on August 18, 2014, 11:31:52 am
Quote from: ianobi on August 09, 2014, 05:57:44 am
The problem is the label "Telemarketers" contains reserved characters. In a digit map you can use any combination of 0-9,*,#,+,-,A-Z,a-z, except m, M, s, S, x, X which have special meaning in the digit map syntax.
Hate to harp on this, but the default label "ste" contains a reserved character...is it working because it's a system default (maybe hardcoded and not parsed)?
Labels do NOT have reserved characters (m, M, s, S, x, X). "ste" is NOT a system default label (it's a user defined label for Seven/Ten/Eleven) and works because labels do NOT have reserved characters.
ianobi:
I apologise for the confusion. The original problem in Reply #8 was most likely caused by the label "MTelemarketers" not being enclosed in its own parentheses.
@ InetUser - I agree 99% with your comment regarding labels. The exception would be to avoid the upper case "M" in an actual label as anything following the "M" may be parsed as the label. We use many digit map labels with a lower case "s" in - Msp1, Msp2 etc. which does show that in most cases a label can contain a reserved character.
@ ipse -
Quote
I am embarrassed to find problems with my digitmaps after 1 year
I have designed hundreds of digitmaps. When I look back at them there's nearly always improvements that can be made and sometimes there are actual mistakes which don't always show up right away. I'll carry on coding mistakes and all - I can rely on the good folks here in the forum to check my work and point out any errors ;)
ipse:
Quote from: ianobi on August 19, 2014, 01:29:28 am
I have designed hundreds of digitmaps. When I look back at them there's nearly always improvements that can be made and sometimes there are actual mistakes which don't always show up right away. I'll carry on coding mistakes and all - I can rely on the good folks here in the forum to check my work and point out any errors ;)
I find this a VERY friendly forum...and this makes for the complete lack of Obihai reps chiming in to solve actual problems. Definitely it was a criteria in buying a second Obi and recommending it to all my friends and co-workers.
Still...I have no excuse for going for the easy "copy/paste" solution sometimes :)
Thanks InetUser.
InetUser:
Quote from: ianobi on August 19, 2014, 01:29:28 am
@ InetUser - I agree 99% with your comment regarding labels. The exception would be to avoid the upper case "M" in an actual label as anything following the "M" may be parsed as the label. We use many digit map labels with a lower case "s" in - Msp1, Msp2 etc. which does show that in most cases a label can contain a reserved character.
There's no problem using uppercase 'M's in a label name. For example, a label name of "MMM" works perfectly, referenced by "(MMMM)". There's no ambiguity since the parser looks for "(M" to trigger a label reference and treats everything (2-16 characters) between there and a ')' as a label name.
Try it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page