Hi, I've got this trigger someone made for me like 3 years ago to add multiline messages to a text box
Which when used outputs messages like this:
The messages come into the box from top to bottom and eventually go too far down that you have to scroll to see new messages... Is there any way to reverse how the messages come in so the new messages are always at the top?
I think the only way to do this would be to rebuild the entire list every time an update is made. Keep track of the entire contents of the list in a string and then append the new messages to the beginning. Adding a message separator parser to the action may be required for correct reproduction.
Since the entire list is being rebuilt every call, this can be extremely resource intensive for long lists. In such a case you might want to buffer already wrapped list elements into a string array used as a first in last out list. Doing so keeps the scroll length manageable, removes the need to process a long string character by character and keeps execution time well bounded.
You might be able to get the messages to reverse if you create the list box in the UI editor. Use TopToBottom val ="true"/> to get new messages to always appear at the top of the list.
Hi, I've got this trigger someone made for me like 3 years ago to add multiline messages to a text box
Which when used outputs messages like this:
The messages come into the box from top to bottom and eventually go too far down that you have to scroll to see new messages... Is there any way to reverse how the messages come in so the new messages are always at the top?
I think the only way to do this would be to rebuild the entire list every time an update is made. Keep track of the entire contents of the list in a string and then append the new messages to the beginning. Adding a message separator parser to the action may be required for correct reproduction.
Since the entire list is being rebuilt every call, this can be extremely resource intensive for long lists. In such a case you might want to buffer already wrapped list elements into a string array used as a first in last out list. Doing so keeps the scroll length manageable, removes the need to process a long string character by character and keeps execution time well bounded.
You might be able to get the messages to reverse if you create the list box in the UI editor. Use TopToBottom val ="true"/> to get new messages to always appear at the top of the list.