jomo wrote in Thu Sep 29, 2016 9:54 am:This touches our general disagreement: I cannot see any advantages in a "flightstrips-bay" that offers unique spaces for different ATC-taskes - when all those tasks must be performed by 1 ATC!
Actually this is, well, I won't name it a disagreement but more different experiences: There are sometimes other ATCs at my airport or in my radar range, so I do share tasks with other ATCs.
On the other hand I experienced aircrafts being parked at my airport or other ground vehicles like FollowMe, motor cycles etc. And I want them separate from the regular ground activities.
Then there are sometimes copilots or passengers. Have you ever controlled a passenger? I want to have those "co-flights" separate from the regular flights.
In KSFO you can often find a carrier. Not a problem in EDDF I guess. But near the coast there might appear a carrier.
Then there are some helicopters, balloons or blimbs which should be handled different from planes.
This is some of the diversity I realized during my ATC sessions.
So your conclusion is correct: The traditional layout seems to be best suitable for you. And that's the layout that is default after downloading and installing. Noone is forced to use different sections or any of these features.
jomo wrote in Thu Sep 29, 2016 9:54 am:I would like to define more support for the "traditional" way, e.g. in regards to
* color (maybe the most left "blue" should change to the now most right "green")
* sorting automatic within those columns e.g. by distance, priority,
* etc.
For
color see a previous post. I either didn't like them, so I changed them for my personal version in code. Actually I use the color of the contact in the radar screen to show me the altitude. Examples: If a contact is red then it is (almost) down to the ground. If there are 2 contacts with the same color near to each other, then this is (or might become) a conflict situation.
In this example from the wiki-page you can see "
sort by distance" (for more information:
http://wiki.flightgear.org/OpenRadar:_Flightstrips-Bay#Configure_a_section)
OK, you found the "bug": There are 3 values in conflict with each other: 1. the maximum width of the flightstrips-bay, 2. a fixed width for the spacer for each column and 3. the minimum width of a flightstrip required to show all labels and fields.
The flightstrips-bay is still at the width of a 3 column design. But as "Ground" section has 5 columns, Java produces an error when a flightstrip is in this section.
Actually I don't know how I can calculate the minimum required width of a flightstrip for different operating systems and fonts. But I keep that problem in mind.
Simple solution: Just increase the width of the flightstrips-bay by dragging the vertical white bar to the left. The layout will restore immediately. A 3 column layout like traditional won't have this problem.
jomo wrote in Thu Sep 29, 2016 9:54 am:May be we could do that as done previously: All Inputs are take when the mouse-pointer exits the FlightStrip. Because then you can do multiple changes to one FlightStrip - and take them all at once. Hitting Enter is an extra, not needed action - and is often destroying the action-string if updating several data in 1 FlightStrip (e.g. hdg + alt + ++ - just by TABmovement).
There is no previously as you couldn't enter anything on the previous flightstrips.
It was/is a dialog which you leave when clicking outside the window or when you hit enter in e.g. remarks.
Have you tried TAB movement? It opens the context menu.
With the first ENTER you tell the program that you've finished your entry and it creates a chat message for you (which you can edit as the keyboard focus is moved to the chat edit field). With a second ENTER you can send this message.
So you type FL200 [ENTER] [ENTER] and the following text message will be sent:
Example: D-1234: Climb and maintain FL200
When you see the created chat message, then you know that you hit ENTER.
The version you are testing is a preview version not the official release, so those descriptions and pictures are still valid for the official release.
For the preview release there are the informations and links in this thread.
When the preview release becomes the official release after being accepted by the ATC community, then we can remove/replace the outdated informations and pictures.
One step after the other