When I said "quite troublesome", I meant it was quite troublesome for my users (a little bit confusing for non-advanced users, like what Absorbation said)...it's not troublesome to code
quote:
Originally posted by CookieRevised
\d is parsed as the delimiter
\n is parsed as a linefeed
\t is parsed as a tab
\? (where ? is any other character) is parsed as taking ? literally
I wonder if you do need a tab-space or a newline in such a small notification window - but this is a good idea and I'll do it (for fear that there is geeeeeeeeek Hopper users, of course
).
And!! \d being the delimiter sounds quite fine for me actually...
And all these being taken as the escape sequences I think there is no need to configure them in HCC
Anyway, thanks for your input, Cookie and others
Now this is what I have in mind... I'll have \d for the delimiter, \n \t as linefeed and tab respectively and if the character following \ is nothing special I'll print the character (without the backslash).
Any comments?
What I want is everything to be easy and straightforward for my users - that is, they can do what they want to do with only reading the least documentation (or tooltip contents, whatever).
Hopper's users don't have the chance to "experiment" with it... If they wrongly run Hopper's command and get undesired results, they are stalled by AFP and have to wait for minutes before they can run another one.