Tyrion 72 Posted April 10, 2016 Share Posted April 10, 2016 Hello, I just updated my PFPX to v1.25. I uninstalled the old version using the windows control panel, then used the full 1.25 installer to get the latest version. Running this version, I had a problem with the 'Flight' and 'Callsign' fields when creating a new flight: When clicking the arrow next to the 'Flight' field, the list takes up the entire height of the screen, and is not scrollable. (Not sure if scrollable is a word, but you get the meaning) When clicking the arrow next to the 'Callsign' field, the list starts under the field as it should, but it's also not possible to scroll though the list. Also, with both lists, there is no live updating when typing as there was in the previous versions. I ran into this problem as I was trying to create a Qantas flight plan. I entered a "QF ..." code in the 'Flight' field, but the system forced the Callsign field to an "EAQ ..." code for Eastern Australia Airlines, while I wanted to use "QFA..." for Qantas. (Both use the QF IATA identifier) The only way for me to change it was to delete it, and manually type the correct one. And being careful not to touch either field again, or PFPX would force it back... (with the manually entered info, the flightplan compiles correctly with the Qantas titles) Is this problem limited to my system, or is it a bug in the update? More information: Windows 7 Ultimate 64 bit PFPX v1.25 fresh install in "C:\Program Files\Professional Flight Planner X" User data in "C:\Users\Public\Documents\PFPX Data" Thank you for looking into this. Please login to display this image. Please login to display this image. Link to comment Share on other sites More sharing options...
FlightSimSoft.com 283 Posted April 10, 2016 Share Posted April 10, 2016 Hello, unfortunately we can´t reproduce your issue, anyone else who experience that? Best regards, Judith Link to comment Share on other sites More sharing options...
Tyrion 72 Posted April 11, 2016 Author Share Posted April 11, 2016 Hey Judith, Thanks for looking into it. I managed to get it fixed by uninstalling and reinstalling v1.25. So it probably was something that went wrong either during installation, or just in Windows being Windows. It appears to work fine now, so... Sorry to have bothered you, Link to comment Share on other sites More sharing options...
Deputy Sheriffs Tom A320 4915 Posted April 11, 2016 Deputy Sheriffs Share Posted April 11, 2016 Because we believe this topic has been answered we have closed it. If you have any more questions feel free to open a new topic. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.