Community Event / Creation TradeDangerous GUI front end

WombatFromHell

W
NoTones said:
[Request] --start-jumps STARTJUMPS, -s STARTJUMPS
Be added,

found myself in a useless trade route earlier and had to resort to cmdline [ or a cmdline prefix box that we can add our own unsupported options into ]
Click to expand...

That functionality already exists. Look closely underneath the destination box on the left side with the Run command selected.

(Edit: End jumps are also supported when any destination is specified.)
 
Last edited:

NoTones

NoTones
WombatFromHell said:
That functionality already exists. Look closely underneath the destination box on the left side with the Run command selected.

(Edit: End jumps are also supported when any destination is specified.)
Click to expand...

:eek: so it does thanks, guess I really do need to get my eyes checked again soon! ;)
 

NoTones

NoTones
[Bug] Switching to Rare then back to Run removes my Avoid data

"Reloading the config restores them" if I forget and save a new config they are lost forever, or until restored from saved notes f'now, until fixed!
 

WombatFromHell

W
Just a status update on why 1.0.5.3 is taking so long. I've been working on adding EDSC support, and I'm kind of stuck fighting with the GetSystems API. It doesn't return sensible results for known systems most of the time, yet Submit works fine returning those same systems. I'm continuing to work on it though, but it's probably going to take me a bit longer to figure out why it isn't working properly.

So, here is what I plan to do in the meantime: I'll continue working on EDSC support in a separate branch until I get it working properly, if you're brave and want to mess with it you can compile the EDSC branch with Visual Studio Express 2013 (instructions are in the FAQ). Normal fixes/features will stay in the master branch until I get that mess sorted. The sooner I get EDSC support fixed, the sooner I can add JumpLists and some other features I'm working on to help with determining if a route is more/less efficient when compared to a saved route.

TLDR; I'll be posting v1.0.5.3 sometime this week, as well as making a new branch for EDSC support while I work out the bugs that are preventing me from merging EDSC submit/get support.
 
Last edited:

WombatFromHell

W
Version 1.0.5.3 is rolling out now. Let me know if there's any general weirdness in the cr/t/hr estimator in mini-mode. From the testing I did during the past few days it seems reasonably accurate for a ballpark estimate (taking into account that I can't easily predict fuel scoops and such).
 

NoTones

NoTones
See post in the TD thread https://forums.frontier.co.uk/showthread.php?t=34986&p=2118657&viewfull=1#post2118657
New TD command --loop-int

just landed 1.8.2 which adds "--loop-int", this lets you specify that you don't want to go back to the same station in less than X hops, e.g.

Code: 
trade.py run synteini/lager --pad L --hops 6 --sum --ls-max 4000 --stock 10000 --ly=42 -li=2
will find routes that requires at least 2 hops between returns to a given station

A->B->A->B <- not allowed
A->B->C->A <- allowed
 

WombatFromHell

W
Version 1.0.5.4 is rolling out now with support for "--loop-int", EDSC submission/recents/lookup support, and some assorted fixes and cleanups for the UI.

(Edit: Just a friendly note: if you decide to use the EDSC submission feature, please be careful about typos in your inputs to avoid sending garbage to the EDSC database.)
 
Last edited:

hitchhiker54

hitchhiker54
1.5.0.4 : After entering an unknown to db system the beeping doesn't always stop until you leave the system again or uncheck the unknown system notification. It's pretty annoying.

- - - Updated - - -

1.5.0.4 : Sample output from submit to EDSC


Origin: HYDRAE SECTOR IH-V B2-0

Status: System coordinates identified.
System: Achenar
Dist: 2
Status: Distance added.
System: Lave
Dist: 3
Status: Distance added.
System: Mokosh
Dist: 1
Status: Distance added.
System: Sol
Dist: 1
Status: Distance added.
System: Gateway
Dist: 8
Status: Distance added.
System: Sol
Dist: 1

The single digits sent are the first digit of the distance only so all coordinates are incorrect :(
 

WombatFromHell

W
hitchhiker54 said:
1.5.0.4 : After entering an unknown to db system the beeping doesn't always stop until you leave the system again or uncheck the unknown system notification. It's pretty annoying.

- - - Updated - - -

1.5.0.4 : Sample output from submit to EDSC


Origin: HYDRAE SECTOR IH-V B2-0

Status: System coordinates identified.
System: Achenar
Dist: 2
Status: Distance added.
System: Lave
Dist: 3
Status: Distance added.
System: Mokosh
Dist: 1
Status: Distance added.
System: Sol
Dist: 1
Status: Distance added.
System: Gateway
Dist: 8
Status: Distance added.
System: Sol
Dist: 1

The single digits sent are the first digit of the distance only so all coordinates are incorrect :(
Click to expand...

Hmm.. I'll see if I can get a maintenance release out today or tomorrow to fix that and a few other issues that snuck in.

(Edit2: The notification bug is hilarious. Very annoying, but also hilarious. I'll definitely fix that ASAP.)

(Edit: After taking a quick look at the code in EDSCClass it seems that distances in the form of "9999.99" are sent properly. It happens to be the regex for prettifying the response that is reporting an erroneously rounded number. So it's only a visual error, not a data entry problem, thankfully.)
 
Last edited:

WombatFromHell

W
I managed to get a bit of time to myself today, so maintenance release v1.0.5.5 is rolling out now. It should fix most of the current outstanding issues (at least the ones I know about).

I'll be working on improving the interface for working with EDSC, and hopefully adding JumpList support (for pinning the app to the taskbar, and quickly opening specific config files), over the next several versions.

I'm open to suggestions anyone may have for improving the EDSC interface, BTW.
 

WombatFromHell

W
After a fair bit of research, some prototyping, and trial-and-error I've come to the conclusion that adding JumpList functionality to the pinned taskbar icon (in Windows Vista or above) would create an unnecessary redundancy and worsen the maintainability of the code. Basically, the functionality a JumpList is intended to provide already exists since v1.0.5.4 in the form of automatically loading the last used config.

If you'd still like me to add JumpLists for recent config files let me know here or in the issue ticket, and I'll see what I can do. In the meantime I'll continue to work on improving the EDSC interface. Arguably this feature could use some more work to make it easier to use so more people will help in adding newly discovered systems to the EDSC database so Trade Dangerous can then leverage that info.
 

WombatFromHell

W
Version 1.0.6.0 is rolling out now. Mostly bug fixes, improvements to the ShipVendor mode, support for "--shorten" in Run, and you can now insert EDSC credited systems into the System.csv directly from the output panel in the EDSC lookup/recents mode. Simply triple click the TD formatted system line below each result, then use the context menu option to insert.

Let me know if you encounter any oddities when TDHelper touches the System.csv.
 

NoTones

NoTones
Where do I get information on --station --confirm, CONFIRMATION CODE for station updates, > "4 character hex confirm code"

I've started visiting stations that have data missing and would like to start using this feature.
can't find any help about using it except the usual trade.py station -h but that does not give any info about where to get the confirm code or how to use it.

I've searched the TD thread and wiki and found no help, thought I'd ask here as its a feature you have included, any help or link to info would be appreciated thanks.
 

WombatFromHell

W
NoTones said:
Where do I get information on --station --confirm, CONFIRMATION CODE for station updates, > "4 character hex confirm code"

I've started visiting stations that have data missing and would like to start using this feature.
can't find any help about using it except the usual trade.py station -h but that does not give any info about where to get the confirm code or how to use it.

I've searched the TD thread and wiki and found no help, thought I'd ask here as its a feature you have included, any help or link to info would be appreciated thanks.
Click to expand...

If you attempt to add/update conflicting info for an existing station Trade Dangerous will prompt you to re-run the command with a confirm code comprised of 4 hex characters. In most circumstances you won't need this code to add/update information for a station.
 
You must log in or register to reply here.
Back
Top Bottom