Nathan,

Sorry to keep adding more ideas but, in addition to the things in my earlier email, could there be a "ppTrouble" variable (for serious problems that kept a horse from running its best)?

No more ideas this week, I promise...

Lou

Yes, but its hard to determine what "trouble" is. Currently the "pace line picker" algorithm looks for key words - stumbled, hesitated, etc., when it finds them it considers the paceline "troubled" for the purpose of selecting pace lines.
I could use the same algorithm to mark the pace line, and then you could get at that info via the ppTrouble variable that you suggested.

A better way to do it would be to have a dialog somewhere where you could:
A) Create your own list of "trouble" key words.
B) Have a set of other "trouble/bad trip" indicators that you could activate/de-activate from said dialog.

There's a little work there, so I'm not sure when I'll be able to insert it. In the meantime, how about a list of common trouble key workds as well as non-comment based indicators for bad trips?

Nathan,

Sure, anything would help - don't hurt yourself though - there's plenty to chew on already...

Lou

Actually, the way it's done for the paceline kicker would be fine if that's easiest to do - most of us already know about fell, stumbled, eased, etc.

This is what ES looks for as an "exuse". Its code, but oen can easily see the key words that are searched. If there are any others let me know.

NULL != strstr(lpctComment, _T("stumbled"))
|| NULL != strstr(lpctComment, _T("rider"))
|| NULL != strstr(lpctComment, _T("clipped"))
|| NULL != strstr(lpctComment, _T("fell"))
|| NULL != strstr(lpctComment, _T("bobbled"))
|| NULL != strstr(lpctComment, _T("awk"))
|| NULL != strstr(lpctComment, _T("stopped"))
|| NULL != strstr(lpctComment, _T("distanced"))
|| NULL != strstr(lpctComment, _T("through after"))
|| NULL != strstr(lpctComment, _T("factor"))
|| NULL != strstr(lpctComment, _T("showed little"))
|| NULL != strstr(lpctComment, _T("showed nothing"))
|| NULL != strstr(lpctComment, _T("tripped"))
|| NULL != strstr(lpctComment, _T("gave way"))
|| NULL != strstr(lpctComment, _T("veered"))
|| NULL != strstr(lpctComment, _T("hop"))

You forgot one ....for trouble.....

|| NULL != strstr(lpctComment, _T("ralph bet him obvious loser"))

How about "eased"? Not trouble strictly speaking, but can explain a poor speed rating.

Good one -- I'll add it - may add yours too JR

Checked?

Good one Freddy -- it will be in 5.0.0.8 - 5.0.0.7 was released tonight.

-N