Release [Explorer's Application] Captain's Log

Hi Genar-Hofoen, thank you for your work so far on this great app! I've been enjoying it and recommending it to friends. Unfortunately today it seems I've also encountered the duplicate entry error, and now the app closes once the error message is closed. I did in fact notice that I had a duplicate process running earlier this afternoon. I know of at least one other friend who's encountered the same error.

Not very programmer-saavy, so I'm now at a loss as to what to do to recover my data. I've read through the discussion here but it's still beyond my understanding, the technical editing that was mentioned. Can you advise? Much appreciated and sorry for the trouble!!
 
Hi Genar-Hofoen, thank you for your work so far on this great app! I've been enjoying it and recommending it to friends. Unfortunately today it seems I've also encountered the duplicate entry error, and now the app closes once the error message is closed. I did in fact notice that I had a duplicate process running earlier this afternoon. I know of at least one other friend who's encountered the same error.

Not very programmer-saavy, so I'm now at a loss as to what to do to recover my data. I've read through the discussion here but it's still beyond my understanding, the technical editing that was mentioned. Can you advise? Much appreciated and sorry for the trouble!!

After I try and get CL to make sure only one instance of CL is running, I'll release Beta 7. This will either be today or tomorrow.

See earlier posts where I mention a program called "sqlite administrator" , with a download link, where you can load the DB file in and try to remove one of the duplicate entries.

Make a copy of the database file and work from that, then after you save the DB file, close sqlite admin and try to run CL again.

Regards
 
I installed 1.0.6 today and after starting the DB I get the following message:

djemCcn.jpg

Tried to uninstall and reinstall it, wouldn't work.
The programm then vanishes, except the process is still there in the Processes Tab of the Task Manager.
 
Last edited:
Hi there.

Another issue from me.
As I have mentioned further up, I run Captain's Log on a seperate PC, and have shared out my logs folder to give Captain's Log acces to the Log files.
Well, this causes a small issue I believe.

CaptainsLog error 3.PNG

Captain's Log reports that Elite is not running and doesn't start the log parser.
Any chance functionality could be added to start/stop it manually by clicking on the log parser info box?

As is, I have to force Captain's Log to reread the entire logs folder.
 
About this "Double Entry" thing: I could repair the DB with SQLite Admin (hopefully). The issue is somewhat confusing, partially because of the overlay I guess. The overlay icon disappeared after some 'back and forths' so I thought I accidentally closed it. I restarted the program and that was when I had two CL exe processes in my Processes tab of the Task Manager. So I guess that I didn't close the program in the first place, but that the icon top left just "vanished". That could have triggered the double entry.
 
Hi there.

Another issue from me.
As I have mentioned further up, I run Captain's Log on a seperate PC, and have shared out my logs folder to give Captain's Log acces to the Log files.
Well, this causes a small issue I believe.

View attachment 47534

Captain's Log reports that Elite is not running and doesn't start the log parser.
Any chance functionality could be added to start/stop it manually by clicking on the log parser info box?

As is, I have to force Captain's Log to reread the entire logs folder.

The reason is because I was not envisaging people using Captain's Log in this manner (obviously) ;)

CL detects whether Elite is running by examining the Windows processes and seeing if EliteDangerous32.exe (the actual game, not the launcher) is running. You can see how running Captain's Log on a different machine would make it think Elite isn't running :)
 
The reason is because I was not envisaging people using Captain's Log in this manner (obviously) ;)

CL detects whether Elite is running by examining the Windows processes and seeing if EliteDangerous32.exe (the actual game, not the launcher) is running. You can see how running Captain's Log on a different machine would make it think Elite isn't running :)

I understand what is happening, and it's good programming practice as it minimises use of system resources. Is it an easy thing to add a manual start of the parser, or is that a bigger issue?
 
UPDATE : New version released : 1.0.0 Beta 7

Changelog:

- Can now toggle between overlay mode and standard windowed mode.

- The option for overlay/standard mode is saved: If you exited CL in overlay mode you'll restart in overlay mode

- Captain's Log now checks for the existence of AppConfigLocal.xml. If it doesn't exist, AppConfigLocal.xml will be created, with the necessary option added for enabling verbose logging. It no longer touches AppConfig.xml.

- Ensure the "Are You Sure" question window for deleting a database will appear on top of all other windows.

- Re-enabled the taskbar entry for Captain's Log in the Windows taskbar - this means alt-Tabbing CL works properly again.

- Much better handling of the window focus when in overlay mode. When in overlay mode, the CL window auto-minimises when CL loses input focus - i.e. Alt-Tabbing to Elite: Dangerous minimises the overlay to "CL". alt-Tabbing to CL unfurls the overlay.

- "There can be only one."... Captain's Log creates a lock file in the CL applocaldata directory. If this file exists, then subsequent attempts to run another instance of CL will not succeed.

- Pressing Return in the planet designation will move input focus to the planet type, in Add A Planet mode (i.e. similar effect of pressing Tab). This makes for even more convenience.

- - - Updated - - -

I understand what is happening, and it's good programming practice as it minimises use of system resources. Is it an easy thing to add a manual start of the parser, or is that a bigger issue?

It's not a huge feat. It'll be done in the next release, as I was in the middle of releasing Beta 7 (which has happened right now) and didn't want to delay it any longer. (I have to draw the line somewhere :) ).
 
It's not a huge feat. It'll be done in the next release, as I was in the middle of releasing Beta 7 (which has happened right now) and didn't want to delay it any longer. (I have to draw the line somewhere :) ).

I was not in any way expecting a solution in beta 7. I was hoping for one eventually, time permitting and so on. This is a hobby project and RL always takes precedence so my expectations relate to that. Thank you for considering implementing a fix in the first place.
 
Last edited:
Download SQLite Admin and open your faulty DB. Under "Tables" go for 'systems' and then 'names'.
In the right field, take the 'Edit' tab then go to the very last entry at the bottom. You should see the double entry there. Kill it, save it and then it should work.

Make a backup first.

This error seems to happen after accidentally closing CL and then launching it again while the process is still active in the Task Manager. You then have a 'shadow' CL running and both CLs then make DB entries, which results in said error.

At least that was what I could reproduce on my PC.
 
Last edited:
I understand what is happening, and it's good programming practice as it minimises use of system resources. Is it an easy thing to add a manual start of the parser, or is that a bigger issue?

Just a stupid idea, but may be you can try it...
If you copy/paste a dummy windows program (calculator... minesweeper or whatever) and rename it to "EliteDangerous32.exe"...
May be it will start as a sort of fake ED...
(It probably won't work, but ... not a lot to do to test this)
 
Wow, thanks for the continual improvements!
Sadly, I cannot rep you more.
 
Last edited:
Just a kindly reminder to folks that CL is labelled Beta for good reason :)

It's still in its early stages of being developed, which means I'll be trying New Things out, and it also means there will be bugs (such as being able to run more than one instance of it at the one time - for which a fix was introduced at the recent Beta 7).

I do try to ensure the database format won't change, and try to catch any huge bugs before CL leaves the factory floor, but as with all software, you make one change which seems great and it affects something else, and then I get a frowny face ;)

Having said all that - I really do appreciate all feedback, as I can't possibly account for all use cases (e.g. running CL on a different machine from the one ED is running on - that one was an interesting surprise to me ;) ), and bugs you see could affect my use of CL as well. So far your feedback has been top notch, so, keep 'em coming :)

For the next release, I am going to begin work on a new method of inputting planet types. I suspect this will take a while to do.

Regards,

Genar
 
Last edited:
Back
Top Bottom