+ thanks I can start using that feature now.
[BUG] towards seems to have stopped working
Community Event / Creation TradeDangerous GUI front end
- Thread starter WombatFromHell
- Start date
+ thanks I can start using that feature now.
[BUG] towards seems to have stopped working
Towards requires a destination before you can toggle it.
I just noticed a bug there. Towards can be toggled on, but not off in certain situations. I'll look into it.
(Edit: In the meantime you can work around the bug by toggling Loop or Shorten to disable Towards.)
(Edit: In the meantime you can work around the bug by toggling Loop or Shorten to disable Towards.)
Last edited:
I should have been more specific (I hadn't tried toggling) but it doesn't add the --towards into the command line
(Edit: You seem to be correct. It isn't properly adding the --towards option.)
Last edited:
Version 1.0.6.2 is rolling out now. This release should fix all the stuff that breaks when using Trade Dangerous v7.0.0 and up. Also some miscellaneous bugfixes and new filtering options for a few commands.
(NOTE: This version breaks TreeView compatibility with any version of Trade Dangerous prior to v7.0.0. Make sure you update Trade Dangerous to the latest git version before using this release!)
(NOTE: This version breaks TreeView compatibility with any version of Trade Dangerous prior to v7.0.0. Make sure you update Trade Dangerous to the latest git version before using this release!)
Last edited:
Absolutely, I'll see if I can get an update out this week. Busy with work lately.
I'm also currently planning out how to add a better rare trading function since TDHelper is pretty close to near feature parity with TD's command line. I got stuck the last time I tried working on that feature, and decided to dedicate my time to improving other parts of TDHelper. I'm not an expert in graph theory so I'm having to learn as I go.
Maybe two more proposals from my side:
1. Maybe it would be good to add a text field where users can add additional parameters what will be added to the end of your generated tradedangerous command
2. Is it possible that the output window will keep also the previous output from tradedangerous an just add the new out under it that you can scroll in the output window? For example I let td give me a run with more hops, on my way I ocr the market data an import them to td. After that I have to rerun my trade calculation because the output windows only shows the import status. A "clear output" button would be necessary then.
Little bug what I have:
When I close TDHelper and reopen it again it keep several settings like cargo capacity, etc. But it don't keep credits, jump distances, min/max GPT - even when I save the settings. Is this on purpose or a bug?
Otherwise - your tool is awesome! I appriciate your effort.
1. Maybe it would be good to add a text field where users can add additional parameters what will be added to the end of your generated tradedangerous command
2. Is it possible that the output window will keep also the previous output from tradedangerous an just add the new out under it that you can scroll in the output window? For example I let td give me a run with more hops, on my way I ocr the market data an import them to td. After that I have to rerun my trade calculation because the output windows only shows the import status. A "clear output" button would be necessary then.
Little bug what I have:
When I close TDHelper and reopen it again it keep several settings like cargo capacity, etc. But it don't keep credits, jump distances, min/max GPT - even when I save the settings. Is this on purpose or a bug?
Otherwise - your tool is awesome! I appriciate your effort.
In response:
1. I'll think about it, but that sounds like a potentially messy way to handle a rather direct user-interface issue. If you can be more specific about the proposal, and put it in an issue ticket I'll look it over and comment.
2. I had considered implementing something like that very early on (currently only the "Update DB" delegate behaves in a similar fashion), but decided against it in favor of the Notes page and the context menu options (being able to push selected text to a panel, that is). I see what you're getting at. I'll try to consider some options to extend the output log in more useful ways.
3. That sounds like either a bug or a bad config file. I would recommend deleting the config file in question, and letting TDHelper recreate it using the latest version.
Last edited:
Hi,
Could you consider adding a check box that equates to the "--progress" switch? It's a useful indicator if anyone (well, me really!) plots a lot of hops in one trip! That's if you don't implement item 1 of br34ker's request above - i.e. adding "--progress" myself in the text box.
Could you consider adding a check box that equates to the "--progress" switch? It's a useful indicator if anyone (well, me really!) plots a lot of hops in one trip! That's if you don't implement item 1 of br34ker's request above - i.e. adding "--progress" myself in the text box.
Last edited:
I did add "--progress" experimentally very early on, and found that it messed with the output in odd ways so I left it out of future builds in favor of the process timer in the bottom-left of the window (and later on, the notification sound upon completing long commands). If you're not sure what I mean when I say "odd ways", look at the output of the Maddavo importer as an example. It still uses a progress bar when it's not being fed "-q", and every change in that bar takes a line in the output leading to larger files taking considerably more space than necessary. I personally found it messy and unnecessary when compared to the process timer in the window.
I suppose one option is to add support for parsing the progressbar text and converting that to a visual progressbar in the window. I'll look into how I can do that.
Version 1.0.6.3 should be rolling out now with some bugfixes and support in the config for adding custom strings to the Run command-line. TreeView should be fixed in non-US locales as well.
(Edit: If you load an old config and can't find the new ExtraRunParams tag inside the file, just save the config and it should appear.)
(Edit: If you load an old config and can't find the new ExtraRunParams tag inside the file, just save the config and it should appear.)
Last edited:
i added --progress to the config file and I see what you mean about "odd ways"! I'll remove it again and stick with what you have already done....
Last edited:
Version 1.0.6.4 is rolling out now with a few minor bugfixes and code cleanups.
(Edit: I just re-uploaded v1.0.6.4 due to fixing a blocking bug with Shorten in the Run panel. Auto-update should push the corrected archive soon. Thanks for the heads up, Maddavo!)
(Edit: I just re-uploaded v1.0.6.4 due to fixing a blocking bug with Shorten in the Run panel. Auto-update should push the corrected archive soon. Thanks for the heads up, Maddavo!)
Last edited:
I had been meaning to extend recent systems to include all the log files and not just the most recent. I'll add that suggestion to my list for the next version.
I've come to a point where I think I could use some feedback. I'm currently implementing a flight log tab for TDHelper which will be setup in a gridview format (like a spreadsheet) with the following columns: date/timestamp, system/station, distance, and notes. The date/time and system/station will be populated by scraping all the network logs, but the user can fill in distance/notes and save this information to a local database in the same directory as TDHelper.
Does this sound in line with the common features available in tools like EDDiscovery, or maybe someone has some suggestions on improvements? Any suggestions would be much appreciated, as this is the last feature I'll be adding before I plan to push the next version.
(Edit: Initially I probably won't have the option to insert custom systems into the database until a later version. That requires a bit more work to prevent bugs when adding/removing scraped vs custom info.)
Does this sound in line with the common features available in tools like EDDiscovery, or maybe someone has some suggestions on improvements? Any suggestions would be much appreciated, as this is the last feature I'll be adding before I plan to push the next version.
(Edit: Initially I probably won't have the option to insert custom systems into the database until a later version. That requires a bit more work to prevent bugs when adding/removing scraped vs custom info.)
Last edited:
Version 1.0.6.5 should be rolling out now to (hopefully) fix the issues with pulling recent systems since ED 1.3 Powerplay dropped as well as some other enhancements. As usual, see the changelog for details.
As for the flight log.. it's going to need some more time in the oven so I'm delaying it until v1.0.7.0 (hopefully in a week or two based on how much time I get to work on it).
Cheers.
As for the flight log.. it's going to need some more time in the oven so I'm delaying it until v1.0.7.0 (hopefully in a week or two based on how much time I get to work on it).
Cheers.