Hi @TheMightyRaider this is partly done. it is a good step. We can have opened views while we can change the flight or operation.
You can try with a test database setup of mscolab or create a second Flight track.

MSS$ python mslib/mscolab/mscolab.py db --seed
MSS$ python mslib/mscolab/mscolab.py start

look into the seed module for credetentials

When we change the model we need also to update this entry on the plot. This is missing yet in the solution.

Have a look into viewwindows.setFlightTrackModel how it is done for the window title

When showing some of the data from a demo server, the position of the name is overlapped by the other text

Maybe place it right of the plot.

Thank you @ReimarBauer for your feedback, Will fix the issues mentioned!

@ReimarBauer , Pushed a commit with the review changes you had mentioned! Let me know if it looks good on your end!

Sorry about that @ReimarBauer , Thanks for your feedback once again.

• I have pushed a fix for the "repetition of title in topView" issue.
• Regarding "The title not been shown in the LinearView" issue, It does show in my end. Can you guide how to reproduce your graph?

On the place where EPSG was printed there where also optional airdata credentionals on topview shown. The place was for EPSG and that good. Or how does this look now when you select that in the docking widget?

(Select to open control)

On the place where EPSG was printed there where also optional airdata credentionals on topview shown. The place was for EPSG and that was quite good. Or how does this look now when you select that in the docking widget?

For comparing with underlaying data.

Click Server/Layer and add a Server url. E.g. http://open-mss.org (not https)

Then select a layer. The model name should be on the plot too.

@ReimarBauer When the size of the window is small, The text gets crowded.

@ReimarBauer When the size of the window is small, The text gets crowded.

The name is mostly needed on a saved plot / printed plot.

On screen having it at the window title is ok.

I tried putting the title in the bottom left. But now it overlap with the x-axis values during sideview plot.
I feel the plot isn't scaling well when the screen of the window is shrieked, Even the values of the y-axis for the sideview plot are semi hidden by default. @ReimarBauer

I think we should keep on topview the location where we have EPSG for everything besides the model.name

With airdata there can be more text added there and we don't have this and EPSG for the other views

without your change:

On the linearview with data the model.name is gone

ideas are welcome to improve matplotlib/qt visualizations.

I think we should keep on topview the location where we have EPSG for everything besides the model.name

With airdata there can be more text added there and we don't have this and EPSG for the other views

without your change:

@ReimarBauer, I'm not sure whether I got right. Do you mean to say, we keep the model name alone at the top right for all the three views [ side, top and linear ] ?

@TheMightyRaider yes we should have same place for the model name on all three views. Currently at the top right is the best option. The special information EPSG, etc on TopView should be kept on its origin place.

@ReimarBauer, Pushed the changes!

On github is a rule for the CI it did not start for new contributors automatically. I cannot change that.
But you can look locally too.

The tests can ran locally, e.g. https://github.com/Open-MSS/MSS/blob/develop/.github/workflows/testing.yml#L68, https://github.com/Open-MSS/MSS/blob/develop/.github/workflows/lint.yml#L69

@TheMightyRaider look on the flake8 linter, meanwhile I play with the changes

@ReimarBauer , Fixed the linting issues thrown by flake8.

@TheMightyRaider have you seen the opportunity to refactor the sigature of update_info_text ?

@ReimarBauer , Nice find! I have updated the update_info_text function. Sorry about the delay.

Quoting below your earlier comment,

ok, fine

there needs a last refactoring change done. When I look with PyCharm (I guess other have also such options) I see the name parameter is not used anymore and we should change the API and content of update_info_text too.

I don't understand what you meant by API here?

I don't understand what you meant by API here?

We have not defined a public Application Programming Interface. That means any signature change is also an API change.
In that case the function has now less parameters than before.

Ahh okay! Thanks for the clarification!

https://github.com/Open-MSS/MSS/blob/develop/.github/workflows/testing-all-oses.yml, This workflow is failing if I'm not wrong. 😢

If it is because of timeout or mac tests that is not related to your changes.

Thank you for your guidance! @ReimarBauer