Qd status, Prepare the masses for the news

[ken]

We might wait until there is a reason, but that may not be long, as for QD, the one file takes care of everyone.

Or at least that is how it was, who know, but I'd think that is how it will remain.

[314159]

I hear you loud and clear.

Just make sure that you understand the differences and consequences of an outdated mac_qd and an outdated qdinfo.dat, plus the way that InCrease can handle emprotz.dat.

If anyone needs details, feel free to ask.

[treadlightly]

I'll be honest and say that I did not understand this thread at all.  It seemed like it addressed an issue that was specific to EMIII?    Perhaps something a bit more explanatory should be added if/when this gets moved to the general forums.

[susato]

It's not specific to EMIII. It's also central to InCrease. All the displays in InCrease dealing with points anticipated, points per hour etc. are based on the qd files emprotz.dat and qdinfo.dat which have to be updated by the user from time to time to preserve the correct points allocations.  (check your Tools menu in InCrease and hit "download qd updates" for an example)

[jackrabbit]

The issue here is a plain text database file, known as qdinfo.dat, that Dick created. It's now used by a lot of folding utilities including InCrease and EMIII. Without its creator, it won't be updated anymore and so a lot of utilities will be impaired. Apparantly, theWeatherMan of EM-III, has stepped up to the plate to keep providing and updating it.

mac_qd, also created by Dick (I think), is the core app used by InCrease for displaying the unit queue. This app needs to be up-to-date in order to read the queue files.

[susato]

So Larry (TheWeatherMan) will take over maintenance of qdinfo.dat - this is good and should ease everyone's worries.  

Now, what about mac_qd?  Do we need to take steps now to ensure that this code is available and that it can be kept current for use by InCrease as Increase and the folding clients evolve toward future versions?   John, (when) should we attempt to bring Kevin (calxalot) into this discussion?

[jackrabbit]

Just took a look at the qd.c source code file (which is used the source for mac_qd). Man o man, that is some hairy stuff. I'd be doing some serious re-engineering if I had to work with that!

[treadlightly]

Thanks, now I get it.  

[Macaholic]

I would assume Kevin already knows what is going on.  Hit qd update and you get this;

downloading qd updates from calxalot.homeip.net ...OK
expanding...
extracting...
qd/
qd/emprotz.dat
qd/mac_qd
qd/qdinfo.dat

updating files...
mac_qd
emprotz.dat
qdinfo.dat

It's coming from his server, so I would surmise that he is very aware of the situation.

[susato]

Thanks CB, when I last ran it, I didn't notice the "from calxalot.homeip.net" bit.  

Perhaps we don't need to do anything at all?