Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows Print&FileWindowManager screen bounding box does not accurately represent multiple screens. #1497

Open
nrnhines opened this issue Oct 11, 2021 · 1 comment

Comments

@nrnhines
Copy link
Member

See #1487 and the forum comments after https://www.neuron.yale.edu/phpBB/viewtopic.php?p=19226#p19226

Setting up a windows virtualbox guest with two screens and arranging as follows
screen-arrange

Then starting nrngui from screen 1 and popping up a Print&FileWindowManager and placing a Graph window in the top right corner of screen 2, gives
pfwm

Saving a session file, the view of the Graph is

{save_window_.view(0, -80, 5, 120, -406, 1165, 300.6, 200.8)}

Exiting, relaunching nrngui, and loading the session file generates a Graph in the correct position on Screen 2 and the same PFWM arrangement as above.

@philbrooksIII
Copy link

(Following up from my posts as graphpaper on https://www.neuron.yale.edu/phpBB/viewtopic.php?p=19226#p19226)
Here's another example of the issue as seen on a native Windows 10 machine:
Monitors arranged as follows:
image
Putting a graph window at all four corners of each screen appears as follows in PFWM:
image
And saving the session, exiting and relaunching nrngui, then loading the session generates graphs in the positions shown here:
image

Interestingly, negative x coordinates seem to be unaffected, while the negative y coordinates are shifted to y=0 (the boxes above the bounding box are moved down, but those to the left aren't moved right). The example above misses this behavior since only negative x coordinates are probed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants