September 28, 20205 yr Hi, I just installed V2.6.1.3. When I want to export a flight plan the export window ends with the field for the base name. According to the user guide there should be an export and close button further down, but they are not visible even if I resize the window. I can use them by <shift-tab> 3 times to reach the export button and press enter, but it is still not visible. (By the way: It would be nice if you could order the fields for <tab> so that it does not jump around in chaos. 😉 )
September 28, 20205 yr Commercial Member Thanks for the report on the tabbing. I've fixed that for the next update. I cannot make the Export and Cancel buttons not display. What is your screen size/resolution?
September 28, 20205 yr Author screen size/resolution was a good hint. I'm using whqd and as the icons are so small I activated 125% scaling (see image below (this is not my system as I use german version)). And this is causing the problem. But pilot2atc is the only program habing problems with windows scaling option. I hope you can solve this.
September 28, 20205 yr Commercial Member I put one of my screens to 125% and the Export Window shows normally, but bigger. I don't think that is the problem. Dave
September 28, 20205 yr Author I think it only happens if you switch to 125% globally, which requires a logoff/logon. When I switch back to 100% the problem disappears.
September 28, 20205 yr Author Sorry, but this is not a fix. I need 125% as 100% is to small for my old eyes 🙂 I hope we/you find a way to get it running with 125%. I did some investigation on dpi scaling. According to process explorer pilot2atc reports to be per-monitor dpi scaling aware which would mean that it handles dpi changes on it's own (e.g. if you move it from one monitor to another having different dpi scaling settings). But I think your application does not do this. Here is a link about this: https://docs.microsoft.com/de-de/windows/win32/api/shellscalingapi/ne-shellscalingapi-process_dpi_awareness?redirectedfrom=MSDN Maybe you just need to use a system call to tell windows that pilot2atc is not dpi scaling aware.
September 28, 20205 yr Author Correction: It is not a system call, it is a setting in the program manifest file (see link in last post).
September 29, 20205 yr Author If somebody has the same problem: Here is the reason why it happend and how I solved it. I had my system dpi scaling set to 125% which produce a nice sharp look for the application, but does weird thing especially with buttons missing in export window. By setting the system dpi scaling back to 100% and instead setting the display dpi scaling to 125% for all displays the problem went away for the price of having a blurred look as Windows does scale the app on it's own. Thanks to Dave for his time working with me on this. Udo
Archived
This topic is now archived and is closed to further replies.