Jump to content
The simFlight Network Forums
Sign in to follow this  
DaveG

Message Window Position Bug?

Recommended Posts

Hi Pete,

Using FSUIPC 5.113 in P3d 4.0.28.21686.

There seems to be a possible bug in FSUIPC positioning of the green message window (used for ATIS etc). Each time P3d is run and the message window opened it's positioned further down the screen.

I see the location is held in the FSUIPC.ini, and this value is changed when P3d is exited. Here's the relevant part from 3 successive runs:

[Window.Message Window]
Docked=186, 1798, 15850, 261
Undocked=8, 661, 1894, 78
[Window.Message Window]
Docked=304, 2720, 15833, 261
Undocked=8, 661, 1894, 78
[Window.Message Window]
Docked=423, 3642, 15816, 261
Undocked=8, 661, 1894, 78

Each time P3d was run and the ATIS window opened, then the sim was exited. If I run P3d without opening the ATIS (or anything that uses that window) then there is no change to the entries in the .ini.

Share this post


Link to post
Share on other sites
On 9/5/2017 at 8:03 PM, DaveG said:

There seems to be a possible bug in FSUIPC positioning of the green message window (used for ATIS etc). Each time P3d is run and the message window opened it's positioned further down the screen.

I wonder if the screen and client positions are getting mixed up. I'll check this. But tell me, are you by any change running in Windowed mode?  I use full screen more and it appears to work perfectly then (ALT+ENTER swaps between them).

I notice that the x, y position of the top left if changing by 118, 922 (119, 922 in the last case). Could that be the screen position of the top left corner of the P3D Window?

Pete

 

Share this post


Link to post
Share on other sites

Hi Pete, hope you had a good holiday. 

I do run in windowed mode usually although the window is maximised and does not move. I use 2 monitors, one for P3d, with other related programs on the other. 

I'll try full screen tonight and see what happens. 

Share this post


Link to post
Share on other sites

I've found the Window position problem. It was a mix-up between Screen, Window and Client coordinates.

I'm going to have to restrict the Window position and size facilities to undocked windows and docked ones in full screen mode only. There are just too many variables and unknowns for me to deal with sensibly, otherwise.

I've got a few other things to attend to, but it'll be in a release before the weekend.

Pete

 

Share this post


Link to post
Share on other sites

Thanks for looking into Pete. I did try full screen last night, and as you say it works fine there. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

×