Closed jamesg31 closed 3 years ago
GUI is working nicely now
I made 1 comment... I'm not 100% sure I'm correct, but the first time clicking each aircraft, the altitude shows empty, right?
Maybe related, if you click directly from 1 aircraft to the other (without clicking empty space to clear in between), the selected_option doesn't update.
If you look at where we create the gui element, there's a initial value. I have it set to an empty string rn bc I didn't know what to set it initially. That's why it shows up blank when you first click. We should probably just pass the current altitude in I suppose when we create the element when the gui is initialized in the aircraft class.
Thanks for the comment. I was already poking around (commit d7b106f), so I figured out exactly what do once you pointed it out (332d00f).
Feel free to update/rename/etc
I'd like to see this PR finalized and merged before I start looking at issue #3 ... I'd want to use the GUI to pop up a menu with spawning options (I think) for initial testing. Adding it to the debug options... once that's set, I'd be able to consider spawning based on gates, timing, etc
I am fine merging it as it is now (its only meant to be a basic implementation), though it will need to be moved around a bit to resolve the conflicts #25 caused.
Not finished yet, just thought I would create a PR to keep track of progress. I have decided to use the pygame_gui package.
I am having a strange issue that I cant really figure out, when you click on an aircraft the altitude selector shows the last selected value for the entire selector, and only when you click on the selector to open it does the current altitude populate the box. Feel free (please! I am so confused) to take a look because I cant figure it out @AdamJCavanaugh
Closes #2