State machine: a device that can be in one of a set number of stable conditions depending on its previous condition and on the present values of its inputs.

Just curious, Bruce.

Do you -- or have you ever -- used a state machine in your calculations?

Or in developing trading systems?

I think we created a few state machine indicators for customers for StockFinder, but there really isn't a good way to create your own in TC2000 (the PCF Language doesn't have user defined variables to store the state).

I know for example we helped create Darvas Boxes (which use state machine type logic) for a customer in StockFinder at one point, but I really would know of any good way to create Darvas Boxes in TC2000.

Being a programmer, I looked into it a few years back. Interesting concept. Didn't stick with it (unfortunately) long enough to have much to contribute.

Still, ... would be cool if State Machines could be implemented in TC2000.

The possibilities are ... whoops ... out of coffee. Barista!

Haven't thought of State Machines in years, but maybe ...

If you can feed the output list of tickers from one EasyScan as input to the next EasyScan, each scan along the way can represent a state (ie, using EasyScan results instead of variables to store the state).

But it's been hours since my first coffee, so there's probably a big flaw staring me right in the face. :)

Oh yes, state machines and TC2000.  As a programmer, I'm waiting for a memory stack and that all precious GOTO command.  (Maybe with version 17.9999999999999?) We can do wonders with GOTO.  For now, I place values in the WATCHLIST columns, with results then sorted by most important first.