#21 New order history features

[Andrew Woodruff]

The Order History Box should not re-type the text
every round (in order to clear out the old text).
Instead, text that needs to be removed should just be
cut out of the current text. Should look into using
TextArea.replaceRange() instead of just doing
TextArea.setText() each time.

[Andrew Woodruff]

Logged In: YES
user_id=435755

Reassigning this to Mat

[Mat Malone]

Logged In: YES
user_id=437080

Done. Let me know if anything isn't getting removed that
should be or if it's removing too much.

[Andrew Woodruff]

Logged In: YES
user_id=435755

Yeah, it's not reprinting everything now, but can we get it
to remove changed orders too? (so that it's easier to
figure what orders you've issued)

[Ian Turner]

Logged In: YES
user_id=4941

Along those same lines, it should initially be filled with
hold orders for each army.

I'd suggest keeping an array of Order objects, initially
filled with hold orders.

[Mat Malone]

Logged In: YES
user_id=437080

Well I CAN do it the ways you guys are describing.
However, both are relatively complicated things to do.
Ian's suggestion is going to require a significant amount
of code outside of CliOrderTextArea because the default
hold order is never handled by the client. We're going to
actually have to generate all those hold orders fore each
army.

Personally, I think that my time would be better spent
doing testing fixing higher priority bugs or doing more
testing looking for said bugs... Or working on the
milestone.

[Ian Turner]

Logged In: YES
user_id=4941

At this point, the bug is essentially a feature enhancement.
Spend your time on more important things.