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

Tooltip displayed on wrong screen #112

Open
govert opened this issue May 23, 2022 · 9 comments
Open

Tooltip displayed on wrong screen #112

govert opened this issue May 23, 2022 · 9 comments

Comments

@govert
Copy link
Member

govert commented May 23, 2022

However, there is a new weird bug that wasn't there in the previous version. This affects computers with more than one screen. The bug appears in both Excel 2010 and Excel 365. Tested on Windows 10. Only the user functions are affected, but built in Excel functions are fine.

Bug: When you have 2 screens, and make the RIGHT screen the main screen, then when the Excel window is in the left screen, the tooltip gets placed on the other screen rather than next to the cell.

To reproduce: Set your desktop to have two screens. Set the RIGHT screen as the main screen, and put excel into the left screen. When the LEFT screen is the main screen, seems to work fine.

image

Originally posted by @Nik-MO in #104 (comment)

@gmichaud
Copy link
Contributor

I have replicated this issue here as well. Has there been any progress since you opened the issue?

@govert
Copy link
Member Author

govert commented Sep 29, 2022

Hi @gmichaud - No sorry, I've not had a look yet - I'll bump up a bit.

@govert
Copy link
Member Author

govert commented Oct 9, 2022

@gmichaud I've tried to tweak the location code a bit in the new version 1.6.1-alpha2.
The calculations and position tracking are a bit tricky, so I'm hoping nothing has broken. But it seems to work now in the reported problem scenario.

@sshukurov
Copy link
Contributor

@govert we cherry-picked your commit to our fork, but the fix does not seem to be working for us.

@sshukurov
Copy link
Contributor

Debug output:
image

@govert
Copy link
Member Author

govert commented Oct 10, 2022

@sshukurov Can you try with a simple add-in with the NuGet packages 1.6.1-alpha2, and make sure it is the only add-in being loaded into the Excel process when you test?

@sshukurov
Copy link
Contributor

@govert it seems to work correctly when I create an add-in from scratch and reference the relevant pre-release NuGet packages directly.

@govert
Copy link
Member Author

govert commented Oct 10, 2022

@sshukurov I forgot to update the IntelliSenseServer version before pushing the package. That might cause an older version add-in with IntelliSense to remain loaded, if loaded in the same process. But then I can't explain why you'd get the debug output from your add-in. You might want to pull the last commit with the server version update too.

@sshukurov
Copy link
Contributor

@govert I just found our fork contains some additional lines of our own in ToolTipForm.cs - I commented out those and it helped!

Thanks a lot for helping with this.

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

No branches or pull requests

3 participants