Community Event / Creation TradeDangerous GUI front end
- Thread starter WombatFromHell
- Start date
Thanks for such a detailed explanation on how to reproduce the issue. I'll look into it.
About the encoding issue: I'll look into it in more depth over the next few days. As for the SQL error, I think I need to add more sanity checking before I pull station data from the database. Currently, I'm assuming the user is pulling data from Maddavo's DB which includes data for the column "rearm" among others. Obviously that isn't as friendly a process for people that use mainly local data.
Perhaps ypu need to specify the version of TD that people must use. Anybody with an old version with that station data missing can easily upgrade I think.
A fair point. I'll put in a version check as well. Thanks for the suggestion.
(Update: I have a better method to accomplish this. I'm now checking the sanity of querying the columns before doing so. This avoids the issue for regular queries as well, in the case of a corrupted database.)
Also, I'm going to need a little more info on the encoding issue with changing VerboseLogging. Are you saying that the tag isn't being read properly by Elite: Dangerous, or are you pointing at the removal of indent that happens when we touch the file? If it's the latter, I'm planning on fixing that for the next release (it bugs me too).
Last edited:
Okay, v1.04g is up and I think I got all the issue tickets. As long as there aren't any major showstoppers reported I'll be taking a little break over the weekend.
Cheers.
Cheers.
I'm sure I'm doing something wrong, but when I try to build the solution of the newest release I downloaded from git by SourceTree, I receive an error during compilation about being impossible to find any reference to System.data.SQLite on row 8 and a warning about the same reference on row 1697. That wasn't happening with earlier versions I always could compile from git source. Any suggestion?
Don't forget to add a reference to the sqlite library in solution explorer so your using statements can find the library.
A fair point. I'll put in a version check as well. Thanks for the suggestion.
(Update: I have a better method to accomplish this. I'm now checking the sanity of querying the columns before doing so. This avoids the issue for regular queries as well, in the case of a corrupted database.)
Also, I'm going to need a little more info on the encoding issue with changing VerboseLogging. Are you saying that the tag isn't being read properly by Elite: Dangerous, or are you pointing at the removal of indent that happens when we touch the file? If it's the latter, I'm planning on fixing that for the next release (it bugs me too).
Yeah I was referring to the removal of the indent, love the fact that these issues are being fixed in such a timely manor, I very much appreciate what you do.
Alright, so this bugs me, I'm not sure what's up with it, but even with the "force" option unchecked, and selecting "All" rather than "Force all", it always runs the line with --opt force. Also I think you could probably clean up the use of lines for the update as well, Trade Dangerous has some arguments that allow you to download everything with one argument, but with the All update that you have, it runs several different versions of the import commands which update All, one at a time, I just think you could clean it up a tad. Also though, take your break for the weekend.
You're quite welcome. I'm just glad other people find my little tool helpful. I do this as a hobby, because I enjoy programming and problem solving (almost as much as I enjoy Elite: Dangerous, but that goes without saying).
Way back when I first started TDHelper I had an issue come up with the freshness of data during updates. I talked with Maddavo about it, and he basically said that the best way to get the freshest possible data was to do some combination of "usefull" + "use2d" + "use3h" (or a descending pattern starting from the oldest to the newest data) and then to pull the systems/stations/shipvendors (either first or last). Currently, there is no faster/better way than that due to how Maddavo has his database configured to provide updates.
As for the "--opt=force" thing, it's because I use my own internal logic for determining when to pull updates without "Force" being set in the UI. That option just prevents from using TD's Maddavo plugin related logic for handling what data to grab. We have to override it in order to pull data in descending order of freshness.
And as for explaining how the dropdown is intended to work, it primarily controls what CSVs to grab, with a few of the following exceptions: "Force All" is equivalent to the old checkbox "Force", it pulls everything (regardless of age) including all CSVs. "Force" is similar to "Force All" but it allows skipping price data with the checkbox next to the Update button. "None" skips all CSVs, only grabbing price data.
Hope this helps to kind of layout how I intended it to work. I'll try to make the tooltips more useful for the dropdown/update function for the next version. I don't intend to confuse the user, it's just difficult to catch everything all at once when I'm iterating versions as quickly as I have been. I wasn't joking when I said I was still in very active development.
(Edit: I think what I'll do for v1.05 is take the time to write a little wiki FAQ page to help people with similar questions. I was kind of surprised that's how Maddavo intended people to grab his data, and even more so that TradeDangerous doesn't do a better job of grabbing all the appropriate data.)
Last edited:
Okay, just pushed v1.04h. I was more productive than I thought I would be today. Fixed a long standing performance issue with the database refreshes. Hopefully this release is relatively bug free so I can focus on finishing TreeView and mini-mode support over the next week.
It seems you're right. I filed an issue ticket, and I'll be looking into it when I get a chance.
Okay, v1.04i is up. This should just be a minor maintenance version to fix a couple of regressions. This should finally polish off the last of the bugs in this branch. Make sure you check out the known issues message in the OP if you have issues with station names in the recent systems list.
(Edit: Window location bug fixed, it should be fine now. Enjoy.)
(Edit: Window location bug fixed, it should be fine now. Enjoy.
)
Last edited:
Thanks. But "C" button still dont work
Hmm.. Works fine for me. Try deleting your config.xml and restarting? You might double check that your NetLogPath in the config.xml actually points to a directory that contains your Logs folder. If your AppConfig.xml is not in the folder above your Logs folder then TDHelper can't find your Logs.
Same issue even after deleting config.xml and reselecting "trade.py" and "AppConfig.xml" - infact for me the only way i can use this is to install "TDHelper_v1.04a" set configs, then every version upto 1.04f fail.
to install 1.04g i have to ignore the .net error and click continue then save setting from within the app - then everything works again... 1.04h and 1.04i fail to find my location.
log location <NetLogPath>C:\Program Files Games\Frontier\EDLaunch\Products\FORC-FDEV-D-1001\Logs</NetLogPath>
Last edited:
I can't fix the issue without information. Please paste your valid Log folder path, and the path to your valid AppConfig.xml. I'll see what I can do about it.
edited my previous post and added log location let me know if you need anymore info