Community Event / Creation TradeDangerous GUI front end

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>

Is your AppConfig.xml in the directory above the one you have as your path?

The current method I use to find the Logs folder involves looking for a valid AppConfig.xml path and then looking for a Logs folder below it (in 90% or more of the edge cases, that rule tends to apply). If it can't be found, the recent systems list will remain blank. So the first step is locating the right AppConfig.xml, and then making sure the Logs folder is below it.

I'll need both valid paths to fix the code so it works correctly for cases such as yours in the future.
 
Is your AppConfig.xml in the directory above the one you have as your path?

The current method I use to find the Logs folder involves looking for a valid AppConfig.xml path and then looking for a Logs folder below it (in 90% or more of the edge cases, that rule tends to apply). If it can't be found, the recent systems list will remain blank. So the first step is locating the right AppConfig.xml, and then making sure the Logs folder is below it.

I'll need both valid paths to fix the code so it works correctly for cases such as yours in the future.

sry yes "Appconfig.xml" is in "C:\Program Files Games\Frontier\EDLaunch\Products\FORC-FDEV-D-1001"
 
sry yes "Appconfig.xml" is in "C:\Program Files Games\Frontier\EDLaunch\Products\FORC-FDEV-D-1001"

Which exception error are you getting when it can't find the current log? What is the full path of the most recent netLog*.log created in the Logs folder? It shouldn't be having issues if the filename fits the standard, and the Logs folder exists.
 
Which exception error are you getting when it can't find the current log? What is the full path of the most recent netLog*.log created in the Logs folder? It shouldn't be having issues if the filename fits the standard, and the Logs folder exists.

ok so to get you more info i just extracted each version to separate clean folders

1.04a works fine
fresh (no settings exist) 1.04b/c .net error during config setup, also hitting continue and hitting c same error
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Exception: Directory does not exist
at TDHelper.Form1.searchForLogDir(String path)
at TDHelper.Form1.validateNetLogPath()
at TDHelper.Form1.validateSettings()
at TDHelper.Form1.Form1_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
TDHelper
Assembly Version: 1.0.0.4
Win32 Version: 1.0.0.4
CodeBase: file:///C:/Program%20Files%20Games/Frontier/TradeDangerous/TDHelper/TDHelper_v1.04b/TDHelper.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34238 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
1.04f slightly diff .net error
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.FileNotFoundException: Could not find file 'C:\Users\Administrator\AppData\Local\Frontier_Developments\Products'.
File name: 'C:\Users\Administrator\AppData\Local\Frontier_Developments\Products'
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.GetAttributes(String path)
at TDHelper.XmlHelper.getDirectories(String path, String pattern)
at TDHelper.XmlHelper.recurseDirectories(String path, String pathPattern1, String pathPattern2)
at TDHelper.Form1.validateNetLogPath()
at TDHelper.Form1.validateSettings()
at TDHelper.Form1.Form1_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
TDHelper
Assembly Version: 1.0.0.4
Win32 Version: 1.0.0.4
CodeBase: file:///C:/Program%20Files%20Games/Frontier/TradeDangerous/TDHelper/TDHelper_v1.04f/TDHelper.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34238 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml.Linq
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------
Microsoft.CSharp
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.CSharp/v4.0_4.0.0.0__b03f5f7f11d50a3a/Microsoft.CSharp.dll
----------------------------------------
System.Dynamic
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34209
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Dynamic/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Dynamic.dll
----------------------------------------
Anonymously Hosted DynamicMethods Assembly
Assembly Version: 0.0.0.0
Win32 Version: 4.0.30319.34209 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/mscorlib/v4.0_4.0.0.0__b77a5c561934e089/mscorlib.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
1.04g works fine (previously failed if 1.04a config was present) but hitting save fixed that issue anyway...
1.04h/i setup fine config looks same as 1.04g but fails to find location

most recent logs are in "C:\Program Files Games\Frontier\EDLaunch\Products\FORC-FDEV-D-1001\Logs" been that way since premium beta

if it helps my game has never been installed to default location
 
Last edited:
Hmm.. the only thing that changed between v1.04g and v1.04h/i are some delegate changes connected to the Run button. It sounds like there's still a lingering bug in the method that recurses for the correct AppConfig.xml path.

Thanks for digging up the error messages and paths for me. I apologize for the difficulty, but it should be fixable now that I know where the bug is at. Don't hesitate to mention any other bugs you might find.
 
One more question: is any directory within that tree from "Program Files Games" on down to the Logs folder an NTFS junction or symlink? Just curious, because there was a commit between 1.04g and the current version that readded logic to ignore junction points due to potential infinite recursion. If the bug is connected to junction points I'll have to make some adjustments to compensate for it.
 
One more question: is any directory within that tree from "Program Files Games" on down to the Logs folder an NTFS junction or symlink? Just curious, because there was a commit between 1.04g and the current version that readded logic to ignore junction points due to potential infinite recursion. If the bug is connected to junction points I'll have to make some adjustments to compensate for it.

Ah yes i use junction links quite a lot as i have only a 256GB SSD installed to C: but like to use C: as the base for everything... Looks like you found my problem, dunno what if anything i could do to fix that my end as i need my junctions :)
 
Ah yes i use junction links quite a lot as i have only a 256GB SSD installed to C: but like to use C: as the base for everything... Looks like you found my problem, dunno what if anything i could do to fix that my end as i need my junctions :)

I have a similar environment except I keep the launcher on the SSD, instead of on my data drive.

The sparse point "fix" is really just a dirty hack to avoid the infinite recursion issue. I'll add some logic that prevents the infinite recursion, a more informative error message, and remove the limitation on using sparse points. In the meantime here's an experimental version of v1.04i with the reparse/sparse-point filtering removed. Overwrite your TDHelper.exe with the one from this attachment, and let me know if it resolves your issue.


(Edit: I've updated the known issues in the OP if this fix might help anyone else having issues with the same problem.)
 
Last edited:
I have a similar environment except I keep the launcher on the SSD, instead of on my data drive.

The sparse point "fix" is really just a dirty hack to avoid the infinite recursion issue. I'll add some logic that prevents the infinite recursion, a more informative error message, and remove the limitation on using sparse points. In the meantime here's an experimental version of v1.04i with the reparse/sparse-point filtering removed. Overwrite your TDHelper.exe with the one from this attachment, and let me know if it resolves your issue.


(Edit: I've updated the known issues in the OP if this fix might help anyone else having issues with the same problem.)

SSD's are the way to go i use one on C: and D: game is installed on D: apps n stuff go on a 3TB data drive

sadly Test version has the same issue no location found with both the test and the release version,
so opted for using real (non junction) locations and created new config (see spoiler)- still no location found with test or release version

<?xml version="1.0" encoding="utf-8"?>
<config>
<Location></Location>
<Path>G:\ISO\Frontier Elite Dangerous\TradeDangerous\repository</Path>
<PythonPath>C:\Python34\python.exe</PythonPath>
<NetLogPath>D:\Profile\Program Files\Frontier\EDLaunch\Products\FORC-FDEV-D-1001\Logs</NetLogPath>
<ImportPath></ImportPath>
<UploadPath></UploadPath>
<Padsizes></Padsizes>
<Avoid></Avoid>
<Via></Via>
<Hops></Hops>
<Jumps></Jumps>
<Credits></Credits>
<Insurance></Insurance>
<PruneHops></PruneHops>
<PruneScore></PruneScore>
<LSPenalty></LSPenalty>
<MaxLSDistance></MaxLSDistance>
<Limit></Limit>
<GPT></GPT>
<MaxGPT></MaxGPT>
<Age></Age>
<AbovePrice></AbovePrice>
<BelowPrice></BelowPrice>
<Verbosity></Verbosity>
<CSVSelect></CSVSelect>
<UnladenLY></UnladenLY>
<LadenLY></LadenLY>
<Margin></Margin>
<Towards></Towards>
<Circular></Circular>
<Unique></Unique>
<DisableNetLogs></DisableNetLogs>
</config>
 
Last edited:
SSD's are the way to go i use one on C: and D: game is installed on D: apps n stuff go on a 3TB data drive

sadly Test version has the same issue no location found with both the test and the release version,
so opted for using real (non junction) locations and created new config (see spoiler)- still no location found with test or release version

<?xml version="1.0" encoding="utf-8"?>
<config>
<Location></Location>
<Path>G:\ISO\Frontier Elite Dangerous\TradeDangerous\repository</Path>
<PythonPath>C:\Python34\python.exe</PythonPath>
<NetLogPath>D:\Profile\Program Files\Frontier\EDLaunch\Products\FORC-FDEV-D-1001\Logs</NetLogPath>
<ImportPath></ImportPath>
<UploadPath></UploadPath>
<Padsizes></Padsizes>
<Avoid></Avoid>
<Via></Via>
<Hops></Hops>
<Jumps></Jumps>
<Credits></Credits>
<Insurance></Insurance>
<PruneHops></PruneHops>
<PruneScore></PruneScore>
<LSPenalty></LSPenalty>
<MaxLSDistance></MaxLSDistance>
<Limit></Limit>
<GPT></GPT>
<MaxGPT></MaxGPT>
<Age></Age>
<AbovePrice></AbovePrice>
<BelowPrice></BelowPrice>
<Verbosity></Verbosity>
<CSVSelect></CSVSelect>
<UnladenLY></UnladenLY>
<LadenLY></LadenLY>
<Margin></Margin>
<Towards></Towards>
<Circular></Circular>
<Unique></Unique>
<DisableNetLogs></DisableNetLogs>
</config>

Hmm.. this is a real headscratcher. I'm trying to duplicate the error message you posted (using v1.04i) with no success. The error you're getting is something like this:

Code:
[COLOR=#E4E4E4]System.IO.FileNotFoundException: Could not find file 'C:\Users\Administrator\AppData\Local\Frontier_Developments\Products'.[/COLOR]
[COLOR=#E4E4E4]File name: 'C:\Users\Administrator\AppData\Local\Frontier_Developments\Products'[/COLOR]
[COLOR=#E4E4E4]at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)[/COLOR]
[COLOR=#E4E4E4]at System.IO.File.GetAttributes(String path)[/COLOR]
[COLOR=#E4E4E4]at TDHelper.XmlHelper.getDirectories(String path, String pattern)[/COLOR]
[COLOR=#E4E4E4]at TDHelper.XmlHelper.recurseDirectories(String path, String pathPattern1, String pathPattern2)[/COLOR]
[COLOR=#E4E4E4]at TDHelper.Form1.validateNetLogPath()[/COLOR]
[COLOR=#E4E4E4]at TDHelper.Form1.validateSettings()
[/COLOR]

Correct? I've tried moving my folders around to duplicate your environment, and I'm not having any luck getting it to error out like that. I've even deleted any Frontier product folders on my C: drive, deleted my Log folder, and made a stack of junction points in an attempt to force it to error out.

It still does what it's supposed to do. It asks for my path to the AppConfig.xml, which I provide, and it happily makes a blank recent systems list with no error. When I move log files back into the Logs folder underneath the path I selected when starting it, it populates the list without complaint.

If you're getting the error I pasted, then I'm really not sure what to say. It's supposed to avoid doing any recursion if you give it a path that exists and it has access to. Maybe check the permissions on the folder you're giving it?

(Edit: The only other thing I can think of is that the network logs aren't in the form of "netLog*.log" inside the Logs folder. That would be the only reason it couldn't populate the list if you give it a valid path. The format of the log filename is defined inside the AppConfig.xml. If your net log files are named something else I'll have to add it to the pattern in order for it to find them.)
 
Last edited:
I'm in the process of doing a complete reinstall of the launcher/game to try and track down this issue. If I'm unable to figure it out I'll be adding a bunch of telemetry and debug logging to the next version in order to try and track this issue down once and for all.
 
Hmm.. this is a real headscratcher. I'm trying to duplicate the error message you posted (using v1.04i) with no success. The error you're getting is something like this:

Code:
[COLOR=#E4E4E4]System.IO.FileNotFoundException: Could not find file 'C:\Users\Administrator\AppData\Local\Frontier_Developments\Products'.[/COLOR]
[COLOR=#E4E4E4]File name: 'C:\Users\Administrator\AppData\Local\Frontier_Developments\Products'[/COLOR]
[COLOR=#E4E4E4]at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)[/COLOR]
[COLOR=#E4E4E4]at System.IO.File.GetAttributes(String path)[/COLOR]
[COLOR=#E4E4E4]at TDHelper.XmlHelper.getDirectories(String path, String pattern)[/COLOR]
[COLOR=#E4E4E4]at TDHelper.XmlHelper.recurseDirectories(String path, String pathPattern1, String pathPattern2)[/COLOR]
[COLOR=#E4E4E4]at TDHelper.Form1.validateNetLogPath()[/COLOR]
[COLOR=#E4E4E4]at TDHelper.Form1.validateSettings()
[/COLOR]

Correct? I've tried moving my folders around to duplicate your environment, and I'm not having any luck getting it to error out like that. I've even deleted any Frontier product folders on my C: drive, deleted my Log folder, and made a stack of junction points in an attempt to force it to error out.

It still does what it's supposed to do. It asks for my path to the AppConfig.xml, which I provide, and it happily makes a blank recent systems list with no error. When I move log files back into the Logs folder underneath the path I selected when starting it, it populates the list without complaint.

If you're getting the error I pasted, then I'm really not sure what to say. It's supposed to avoid doing any recursion if you give it a path that exists and it has access to. Maybe check the permissions on the folder you're giving it?

(Edit: The only other thing I can think of is that the network logs aren't in the form of "netLog*.log" inside the Logs folder. That would be the only reason it couldn't populate the list if you give it a valid path. The format of the log filename is defined inside the AppConfig.xml. If your net log files are named something else I'll have to add it to the pattern in order for it to find them.)

sorry alot of posts have gone by,
the .net error last appeared in version 1.04f - since that version no error msgs 1.04g works great and h/i/test versions just fail to get location (no error msgs).
 
sorry alot of posts have gone by,
the .net error last appeared in version 1.04f - since that version no error msgs 1.04g works great and h/i/test versions just fail to get location (no error msgs).

So, basically, you have the correct NetLogPath set, but the recent systems list remains empty? I think I may know why. There's a small error in how I'm parsing the net logs. If you play in any other mode aside from Open Play the string that holds the current location has a small difference.

Here's an example, in solo mode:

Code:
{13:10:39} FindBestIsland:USERNAME:solo:StationName:SystemName

And in Private Group mode:

Code:
{13:16:45} FindBestIsland:USERNAME:48964:StationName:SystemName

And in Open Play mode (the one I'm currently parsing for):

Code:
{13:18:15} FindBestIsland:USERNAME:all:StationName:SystemName


So.. I think the mode ID (between the username and the StationName) in the string is the issue. I'll need to make some adjustments to the regex I'm using to catch those lines, as I'm only catching the one in Open Play at the moment. I'll have a build that fixes that issue out in a little bit.
 
Last edited:
I just pushed a new build, v1.04i_re. This should solve the empty recent systems list, as it fixes the error I just mentioned. Let me know if that solves your problem.

I'll still be taking a look at how I do directory recursion for v1.05 though.
 
I just pushed a new build, v1.04i_re. This should solve the empty recent systems list, as it fixes the error I just mentioned. Let me know if that solves your problem.

I'll still be taking a look at how I do directory recursion for v1.05 though.

Yep seems to have done the trick more +Rep coming your way as soon as forum lets me
 
Yep seems to have done the trick more +Rep coming your way as soon as forum lets me

Thanks for sticking with me through that debugging process.

Pulling stations and systems straight out of the net log is a very new feature. It kind of figures there would be some nuances to adding support for it. I probably should have tested more edge cases before I released it.
 
Just pushed v1.04i_re2 to fix the import/upload buttons that I broke with a silly typo the other day. Oops..

If you happen to have that issue, go grab the latest version to fix it.
 
Just pushed v1.04i_re2 to fix the import/upload buttons that I broke with a silly typo the other day. Oops..

If you happen to have that issue, go grab the latest version to fix it.

I don't use TD import as I use EliteOCR export to EDDN - but will grab and test
I do however like to Pin my most used apps to the taskbar, is there anything you can do to make this Pinable? (not a big issue)

Just added your app to
Complete list of all third party tools, spreadsheets, manuals and other data sources Thread
 
Last edited:
Back
Top Bottom