[MakeshiftWalrus]

It appears that the new writing indicator only works if you write using this input bar.


Could we have it for these as well?




That'd be appreciated for us few that use them.

[Soapy]

Very much so.

[Neus]

This isn't likely the change; it would require say to bring up the input box always instead of being able to type into the input bar, which is obviously undesirable.

[Rendar]

If you're not using macros to type stuff out, you're being horribly inefficient.

[MakeshiftWalrus]

Rendar » Sun Apr 26, 2015 6:42 am[/url]"]If you're not using macros to type stuff out, you're being horribly inefficient.

To me it's a matter of what you prefer. I for one prefer to use the boxes.

[MakeshiftWalrus]

Neus » Sun Apr 26, 2015 6:23 am[/url]"]This isn't likely the change; it would require say to bring up the input box always instead of being able to type into the input bar, which is obviously undesirable.

You can't have two different lines of code? One for the input bar which triggers whenever text is written in it and one for the input box which could trigger whenever it was present on the screen regardless of it being typed in or not?

[Kippeh]

As for me, I just tie the command into macros and it's much more faster. :> Extra codes are unnecessary.

[Neus]

MakeshiftWalrus » Sun Apr 26, 2015 11:16 am[/url]"]

Neus » Sun Apr 26, 2015 6:23 am[/url]"]This isn't likely the change; it would require say to bring up the input box always instead of being able to type into the input bar, which is obviously undesirable.

You can't have two different lines of code? One for the input bar which triggers whenever text is written in it and one for the input box which could trigger whenever it was present on the screen regardless of it being typed in or not?

This isn't that simple. The input box shows up because of the way BYOND handles verbs with arguments (if the argument is empty, it will show the text box). I have no way to reliably detect when that input box is being shown.