Yes I noticed it. It would be great if SambaPOS can throw a exception though. I circumvented the problem and I am not sending special characters any more but still I think the exception would help
I understand why SambaPOS won’t always throw an exception on these types of formatting issues, reason is certain content may be entered by end users without knowledge of special characters, like product names, entity data, etc. If you throw an exception on any such error during printing a template, you end up it doesn’t print, whereas handling the exception and still printing is desired in most situations.
I would however suggest it would be good if the exceptions can be logged and retrieved somewhere, as I have had to deal with similar situations in the past and it’s not always easy to debug the template when no exception is thrown. Maybe a logging option? @emre
SambaPOS will catch a bracket issue here and display a warning when you print preview it.
<C8>Text: {CALL:utl.echoText('{abc')}
However this is a valid syntax.
<C8>Text: {CALL:utl.echoText('{abc}')}
SambaPOS will render {abc} to nothing as there is no registered handler for abc. I won’t attempt to validate tags as they may contain expressions and will probably generate false warnings for some cases.