Hotstring() function with label or function vs Ending character

[JnLlnd]

Not sure if this is the desired behavior or if this should be considered as a bug.

When you type an hotstring trigger with default options, the ending character is kept after the hostring is expanded. For example, with the code below, type "btw" and Enter and the expanded "by the way" string will be followed by a new line. Type "btw" and Space and the expanded "by the way" string will be followed by a space.

But if you use the new Hotstring() function with the same default options, the ending character is not kept. It is as if the "O" (Omit the ending character) option was used. But it is not. Same behavior when using a function instead of a label.

Is it a known limitation of the Hotstring() function or a bug?

Thanks.

Code: Select all

Hotstring(":X:asap", "TypeASAP", On)
return

::btw::
send, by the way
return

TypeASAP:
send, as soon as possible
return

[swagfag]

what?

in the example u provided, typing 'btw' followed by space or enter will not result in 'by the way' + \n or \s. youre using send to type the characters, the hotstring flags have no bearing upon what Send does.

[JnLlnd]

Oh ;-) I first tested it with the format ::btw::by the way then changed last minute to using Send. (never do :-\ )

So it is not using the Hotstring() function with a Label or a Function that cause this but the use of Send. I see...

This was awkward, but it replied my question :-)

[JnLlnd]

And thanks, swagfag.

[lexikos]

It is not the use of Send which causes this. If you don't send anything, you still won't get the ending character.

It is the difference between auto-replace hotstrings and other hotstrings. Auto-replace hotstrings send the replacement text and end character. Non-auto-replace hotstrings only perform backspacing by default.

[JnLlnd]

Thanks Lexikos for the precision. Would you consider in a future release to add the "Keep ending character" options for "other hotstrings" (those non-auto-replace)?

[lexikos]

What would you expect the option to do? What if the hotstring doesn't call Send at all, or calls Send multiple times?

If you don't want to erase the hotstring abbreviation and end character, use B0. If you want just the end character to remain, or you want it to appear after text you send, send the contents of A_EndChar.

[JnLlnd]

Ah! Good. The solution is already available: sending A_EndChar.

Thanks.