Post by kelvyn on Apr 11, 2010 12:02:43 GMT -5
Dutch,
Question/Comment #1
Can you look into preventing FS Administrator from closing when you hit the ENTER key? I typically hit the ENTER key to make a selection I made take effect.
Example, when on "Flight Dispatch" I enter the Dep. Airport and A/C Type and any other Options and press ENTER as I was expecting that ENTER would trigger the "Find Flights" and display them to me, but instead it causes the Administrator to exit.
Of course the above comment might be a bit selfish of me, but I do believe it will enhance the flow of the application.
Comment #2:
Congratulations on the "Get Weather" function(s) rewrites as I'm not seeing the same nagging locks as expected from a BETA version that I was previously running.
Question/Comment #3:
Need clarification on the "Wind Direction/Speed/Temp" as the manual states this is the Upper level WND(s)/TMP at the Dept and Dest airports. Now is this the WND(s)/TMP at FL? Or an average you do of some layers?
Question/comment #4:
Can we be allowed in a future update to change the required FUEL and ETE? As I will see this saving some steps on revising ETE inside FSCOM. Also, if the intent is not to be able to update the ETE and/or Fuel Required then it might be a good idea to not use Text Box(s) and to may be Static Label(s), or you can stay with Text Box(s) but prevent editing on them as it give a little false impression that you can adjust them directly.
Thanks very much!!! So far it has been program has been stable on my setup but still poking around so might add additional comments to this thread.
Question/Comment #1
Can you look into preventing FS Administrator from closing when you hit the ENTER key? I typically hit the ENTER key to make a selection I made take effect.
Example, when on "Flight Dispatch" I enter the Dep. Airport and A/C Type and any other Options and press ENTER as I was expecting that ENTER would trigger the "Find Flights" and display them to me, but instead it causes the Administrator to exit.
Of course the above comment might be a bit selfish of me, but I do believe it will enhance the flow of the application.
Comment #2:
Congratulations on the "Get Weather" function(s) rewrites as I'm not seeing the same nagging locks as expected from a BETA version that I was previously running.
Question/Comment #3:
Need clarification on the "Wind Direction/Speed/Temp" as the manual states this is the Upper level WND(s)/TMP at the Dept and Dest airports. Now is this the WND(s)/TMP at FL? Or an average you do of some layers?
Question/comment #4:
Can we be allowed in a future update to change the required FUEL and ETE? As I will see this saving some steps on revising ETE inside FSCOM. Also, if the intent is not to be able to update the ETE and/or Fuel Required then it might be a good idea to not use Text Box(s) and to may be Static Label(s), or you can stay with Text Box(s) but prevent editing on them as it give a little false impression that you can adjust them directly.
Thanks very much!!! So far it has been program has been stable on my setup but still poking around so might add additional comments to this thread.