Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Too many columns of object headings #4

Open
1 of 2 tasks
eAlasdair opened this issue Jun 8, 2022 · 0 comments
Open
1 of 2 tasks

Too many columns of object headings #4

eAlasdair opened this issue Jun 8, 2022 · 0 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@eAlasdair
Copy link
Owner

eAlasdair commented Jun 8, 2022

If a number of locos are being traced, and one despawns, then the columns that the loco occupied are filled with dummy data (headings) until a new loco spawns to take its place - this helps preserve the columns each loco occupies. However if the end loco despawns there's no need for any dummy data, as there's no later loco to fill specific columns. If there's an incident where many locos are spawned at once, and then most of them despawn, the path ends up with far too much of this data.

Secondly, the purpose of the dummy data is for it to be used as column headings, but if no loco spawns to fill that column then again the path ends up with a lot of this dummy data.

The tracer should:

  • Only give those headings in columns the row before an object starts being traced there (if possible)
  • Recognise when all locos for a given row have been reported and stop writing any more information
@eAlasdair eAlasdair added bug Something isn't working enhancement New feature or request labels Jun 8, 2022
@eAlasdair eAlasdair mentioned this issue Jul 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant