Extreme Programming Adventures in C#

Chapter 8. The InputCommand Object

We thought the code was telling us that it wanted another object, so we gave it another object. Was the code then happier? Were we? Read and find out...

Recap

In Chapter 7, we set up an acceptance test that allowed the customer to say where the cursor was in the input and to condition the output based on that result. Then we went down a rat hole and backed out the code. We had identified that we needed an object, and we sketched the way that object would be used. The object we wanted was called InputCommand, and the idea was that it would be able to answer the clean input (the input except with the cursor position indication removed) and the selection start (the location of the input cursor). The code we wanted ...