Community Event / Creation TradeDangerous GUI front end

Mattrik Kin Jarador

Mattrik Kin Jarador
Great work, love the Tree output - it makes the process of travel/unload/load for each step of the way a LOT easier to keep track of.

A few things I've noticed:
  1. Your 'on top' toggle (T) for mini-mode window makes it difficult to distinguish between 'on' and 'off'. I clicked it a few times and finally noticed the 'T' looked slightly different between clicks - are you making it bold? Anyway since it's so small, the effect is hard to see. Perhaps changing its label to ON and OFF, or using colors? Just a suggestion.
  2. The method for going back to full screen mode when in mini-mode isn't obvious. I just tried clicking around the mini-mode window's title bar and finally noticed that if I double click on the TDH icon in the top left corner this takes me back to full screen. Are you intending to have a more obvious control to go back to full screen?
  3. Should there be pop-up contextual help for the 'Run' choice in the TD command drop-down control? This bit is confusing. When TDH is first started, 'Run' is selected by default. Mousing over the control, I see 'Select the command to run'. When I chose something else - like 'Buy' - the mouse-over help text says 'Check nearby for stations selling items' which makes sense. And if I go back to 'Run', the pop-up text still reads 'Check nearby for stations selling items'. This happens for all choices in the list - whenever I go back to 'Run', the help text remembers whatever my LAST choice was before I picked 'Run' and shows that choice's help text.
  4. When selecting 'Buy' or 'Sell', you change the Laden LY: field to Near LY: so we can select the farthest distance to check for buy or sell opportunities, but the mouse-over help still reads 'Distance that can be traveled while fully laden (including fuel)'.

Hope this helps, and apologies if I'm repeating any known issues.
 

WombatFromHell

W
Ahh, good catch on the tooltips. I'll fix them once I'm done adding support for saved Run pages to the TreeView. It gets tricky keeping all the tooltips straight with so many user facing controls.

As for on-top toggling, the button is meant to be as minimal as possible, but your suggestion is very valid. I'll adjust it to be more obvious. I just pushed a commit a little while ago to let the user exit the dialog with the Escape key, and I'll be changing the tooltip to mention this.

(Edit: Version 1.0.5.1 should be rolling out now. It should fix most of the outstanding issues with the initial release.)
 
Last edited:

WombatFromHell

W
So after thinking about Maddavo's suggestion on favoriting of recognized Stations, I may have an idea on how to approach implementing it:

I could add some keyboard shortcuts like Shift+Enter/Ctrl+Enter to the Source/Destination boxes so that when a user enters a recognized station we can push that station to a string that gets saved/deleted to/from the config file.

Anyone have any other suggestions for alternate ways to approach it, or maybe improve upon it?
 

hitchhiker54

hitchhiker54
Having tried some other ED tools, one feature that really sprang out was a popup notification if you visited a system not in the tools database. While I'd be happy to run Trade Computer Extension for this feature alone, I do not own a licence for Excel and nor do I want to buy, rent or pirate one. Would this be a possible new feature? I'm sure it would prompt many new people to add the new systems if they were spared the legwork of checking every jump :)
 

WombatFromHell

W
hitchhiker54 said:
Having tried some other ED tools, one feature that really sprang out was a popup notification if you visited a system not in the tools database. While I'd be happy to run Trade Computer Extension for this feature alone, I do not own a licence for Excel and nor do I want to buy, rent or pirate one. Would this be a possible new feature? I'm sure it would prompt many new people to add the new systems if they were spared the legwork of checking every jump :)
Click to expand...

That's a good suggestion. I'll look into what I can do to integrate adding/checking systems. I had considered adding edsc support, but didn't know if anyone wanted it or not.
 

hitchhiker54

hitchhiker54
EDSC support would be nice, but even just the pop up to let you know you can add a system and help expand the project would be a great plus, maybe with an on/off toggle for those that do not wish to contribute.
 

WombatFromHell

W
Version 1.0.5.2 should be rolling out now, and it fixes the majority of the outstanding issue tickets related to v1.0.5.1.

It adds station favoriting, notifications when entering an unknown system, and fixes/cleanups to the main window and mini-mode. Enjoy. :)

(Edit: Hmm.. unknown system notifications are acting strange. I guess it's a regression. I'll put up a fixed version of v1.0.5.2 in a little bit. Auto-update will silently fail for a bit until I do.)

(Edit2: Should be fixed and working properly now.)
 
Last edited:

NoTones

NoTones
WombatFromHell said:
Version 1.0.5.2 should be rolling out now, and it fixes the majority of the outstanding issue tickets related to v1.0.5.1.

It adds station favoriting, notifications when entering an unknown system, and fixes/cleanups to the main window and mini-mode. Enjoy. :)

(Edit: Hmm.. unknown system notifications are acting strange. I guess it's a regression. I'll put up a fixed version of v1.0.5.2 in a little bit. Auto-update will silently fail for a bit until I do.)

(Edit2: Should be fixed and working properly now.)
Click to expand...

Think you missed a bug, on first loading ED then the GUI (only one system in log) the current button[C] does not populate source, Visiting another system everything is back to normal and populates.

Even with above [C] not working the drop down still works and the system can be selected from the logged entry

Great work on the updates will try to test them later
 
Last edited:

DRY411S

D
With the game 1.2.07 patch today, they seem to have messed about with the verbose logging format, so your prog is no longer picking up the current system name correctly. (EliteOCR is also broken the same way as it happens).
 

WombatFromHell

W
DRY411S said:
With the game 1.2.07 patch today, they seem to have messed about with the verbose logging format, so your prog is no longer picking up the current system name correctly. (EliteOCR is also broken the same way as it happens).
Click to expand...

It certainly seems that's the case. I'll have a fix out in a few hours. I guess I should have waited till after they patched. My mistake.
 

NoTones

NoTones
DRY411S said:
With the game 1.2.07 patch today, they seem to have messed about with the verbose logging format, so your prog is no longer picking up the current system name correctly. (EliteOCR is also broken the same way as it happens).
Click to expand...

Both are working fine for me apart from what i mentioned in post above, check your .xml and visit more than one system and try them again
 
Last edited:

WombatFromHell

W
Yeah, I just checked in all play modes (solo, private group, and then open). It seems to work fine.

I would recommend double checking the path inside the <NetLogPath> tag in your Default.xml. You may also want to double check that VerboseLogging is set properly in AppConfig.xml. TDHelper tries to do that for you (and works properly, from what I can tell), but if you're still having issues that would be what I would check first.

TDHelper can't very well parse logs that don't exist, now can it? :)

(Edit: Although it's probably obvious, make sure <DisableNetLogs> isn't set to true in Default.xml. That would also prevent recent systems from populating.)
 
Last edited:

DRY411S

D
The problem has occurred in only one system so far, it's been fine for others. It might be a 'first run' issue after the patch. It happened in this GUI prog and EliteOCR, both now seem OK.
 

WombatFromHell

W
DRY411S said:
The problem has occurred in only one system so far, it's been fine for others. It might be a 'first run' issue after the patch. It happened in this GUI prog and EliteOCR, both now seem OK.
Click to expand...

Out of curiosity, which system are you having issues with? It could be a parsing issue.

The method I use to grab system/station names involves stripping off garbage from the end of the system/station string. The parsed string typically looks like:

Code: 
"USERNAME:all:Station ABC3:System"

You can see the garbage "ABC3". I think it's related to instancing. The issue derives from overly aggressive matching on that system/station line.

If you have issues with a particular system/station it would help to attach your netLog or that particular line from the log so I can make refinements to the parsing regex.
 
Last edited:

DRY411S

D
This isn't a case of it not having net log switched on, it's a case of the program showing gobbldegook system / station name when it read the log. It seems to have been only the first system I visited after the patch.


It was this system that gave the error. The line in the Netlog is the first FindBestIsland in the file. (If it's significant), it includes the word FRESH whereas none of the others do.

Code: 
{17:35:42} FindBestIsland:FRESH:DRY411S:124886:Ziegel Orbital:Omicron Gruis
 

WombatFromHell

W
DRY411S said:
This isn't a case of it not having net log switched on, it's a case of the program showing gobbldegook system / station name when it read the log. It seems to have been only the first system I visited after the patch.


It was this system that gave the error. The line in the Netlog is the first FindBestIsland in the file. (If it's significant), it includes the word FRESH whereas none of the others do.

Code: 
{17:35:42} FindBestIsland:FRESH:DRY411S:124886:Ziegel Orbital:Omicron Gruis
Click to expand...

Thanks for the extra info. That string when run through the current regex I'm using definitely seems to cause the issue you're describing. I'll make sure it's fixed for the next version.
 
Last edited:

NoTones

NoTones
[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 ]
 
You must log in or register to reply here.
Back
Top Bottom