manual scratch issue

[Ted Craven]

Originally Posted by DanBoals

Ted,

I was perfectly happy with the old version of RDSS.

I wanted you to fix it and get it stable. I did not ask for useless bells and whistles to be added to make it even more unstable. We were losing features like real time odds and results that were important to me at least. I thought trying to add a bunch of silly **** when the basics were not working was frivolous.

You sent me an email, I still have it and can copy and paste it here if you do not remember, and in that email you ask me to download and test the new version. When a friend asks for help, you help them. I downloaded the version, which I did not want, and tested it for you for free. Now it seems like you are pissy with me because I told the emperor he had no clothes... I am sorry, I did not know I was supposed to lie and say everything was beautiful. I thought when you asked me to run it thru the paces you meant that so that is what I have been doing.

I have not been posting any of the bugs in public forums, just on the troubleshooting / bugs forum you put up for these beta testing issues.

I don't know what you think I did wrong but please do not ever ask me for a favor again.

Thanks,

Dan

Dan, I'm sorry you are not enjoying the new version. If you don't need or want the 'bells and whistles' you can revert to the previous version: http://paceandcap.com/forums/showpos...92&postcount=4

In a previous Thread of your first impressions, you commented about repeated crashes during race assembly. My reply was that this was really not a commonly reported scenario so I wanted to observe your experience to help me trouble shoot your problem. My apologies if my wording in that reply "Let me know by email a schedule for connecting you for this."- was ambiguous and you did not know I was requesting you email me to find your best schedule to connect with me in a Zoom meeting to help you troubleshoot this.

Per my above response to Swifty - when I encounter issues I cannot resolve by text questions and answers, I offer to connect remotely by Zoom to observe the issue. I would say that approximately 99% of users who I suggest this to agree eagerly and we get things resolved quickly or I understand more about an issue in order to resolve it. I have dozens and dozens of such remote connections in the past few months - hundreds over the years. I accept you may not wish to do this, for privacy reasons or whatever - and may not wish to give me mouse and keyboard control to troubleshoot. I don't need such control if I can simply get the person to SHOW me what the issue is - Share their screen with me - and respond to my requests to do this, do that, try this, etc, etc. I presume, as a high-level computer user, you would know all of the requests to check things I might ask for.

As I mentioned, I just do not know why you have issues which have not been regularly reported by others. I just do not know what I don't experience - and I can't fix problems I cannot duplicate or even SEE actively failing.

This current version addresses MAJOR issues with interacting with TwinSpires where we got the BPP and PL ratings - and Tote data. The TS Ratings were easier to resolve, the tote data was/is harder. We were NEVER going to (or will ever) get Tote data back in the previous version, however we will get it back in this updated version and underlying platform - soon. You are not the only person eagerly wanting live Tote data back!!

I thought to ask you if you cared to test this new version while it was yet unreleased. I thought you'd be curious. I appreciate your first impression comments in that other thread. Even if they came pretty close to the final release date, I waited for you to make contact with me regarding remote troubleshooting as suggested so we could try to resolve your reported issue before final release, but I never heard from you about that, though we had several other email correspondences about other stuff which I thought I replied satisfactorily about.

If it was unclear about what I was asking regarding remote troubleshooting - well that is unfortunate. The offer still stands - no worries! I do not need to take control of your computer. You can simply share whatever screens you wish to demonstrate the issue - presumably just your RDSS screen. That's how Zoom (and Teams and any other remote meeting software) works. Privacy is paramount and controlled by you.

I have removed you from the Leverage/Pace Pre-testing group email list (though that group is now inactive since we're live with the software). I will not ask you to assist in any future testing or bother you for favours. I WILL try to help you if you are having trouble with RDSS - that is part of my job as tech support guy.

I would say, aside from several ongoing bugs which will be addressed soon in upcoming releases (as expected) - the issues which you and Swifty are reporting have not generally been reported by others. As I mentioned - I am eager to address these. But I need your help. Otherwise, as suggested initially - you are welcomed to revert to the previous version.

Best regards,

Ted

[Swifty0x0]

The Tote checkbox is disabled (greyed out). Am I understanding that you're saying it's safe to leave the Get TS and Scratches checkbox enabled even working races the day before (because the Tote is disabled)?

One of the issues before was when RDSS ended up getting the scratches for the current day even though the card might be a future date, resulting in corrupted entries. Is that not a problem anymore?

[Ted Craven]

Originally Posted by Swifty0x0

The Tote checkbox is disabled (greyed out). Am I understanding that you're saying it's safe to leave the Get TS and Scratches checkbox enabled even working races the day before (because the Tote is disabled)?

One of the issues before was when RDSS ended up getting the scratches for the current day even though the card might be a future date, resulting in corrupted entries. Is that not a problem anymore?

When the Get TS Ratings box is CHECKED, the Get Tote box also gets CHECKED. When Get TS Ratings is UNCHECKED, Get Tote is also UNCHECKED. They are always in sync now. The Get Tote box is disabled (greyed-out) but it is CHECKED, per the screenshot below.



The problem was - some users left the Get Tote UNCHECKED while CHECKING the Get TS Ratings (not unreasonably so, since no Tote data is currently available). However this allowed a scenario like you describe of getting scrambled Entries when working on tomorrow's races in the early hours Eastern time. RDSS uses its (not-quite-ready) Tote checking ability to determine if the tomorrow race your are working on should be checked for available TS Ratings. If Get Tote is turned OFF while Get TS Ratings is turned ON, RDSS does not perform this check and you got weird info.

Hence the synch in the new version. And why you should now trust to leave the Get TS Ratings always checked. RDSS should never be confused and get yesterday's TS ratings for tomorrow's race (early in the morning, while moving between yesterday and today).

It's not a problem anymore.

I hope that clarifies things.

Ted