Bug 1474 - IME candidate window on Windows has offset position
Summary: IME candidate window on Windows has offset position
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: Trunk
Hardware: PC Windows
: Low normal
Target Milestone: ---
Assignee: Mike Krüger
URL:
Depends on:
Blocks:
 
Reported: 2011-10-13 07:20 UTC by Mikayla Hutchinson [MSFT]
Modified: 2013-07-16 12:47 UTC (History)
5 users (show)

Tags: gtk
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Mikayla Hutchinson [MSFT] 2011-10-13 07:20:42 UTC
The IME candidate window on Windows is offset some way below the caret position. This also affects standard GTK+ text widgets, not just the MD source editor.
Comment 1 Mikayla Hutchinson [MSFT] 2013-07-01 14:25:14 UTC
This is a GTK+ bug, seee https://bugzilla.gnome.org/show_bug.cgi?id=663096
Comment 2 Mikayla Hutchinson [MSFT] 2013-07-01 15:24:52 UTC
It should be pretty easy to fix, just replace the GetWindowRect call with DwmGetWindowAttribute if DwmIsCompositionEnabled is true. The only gotcha is that it'll have to be a soft dependency since it doesn't exist on WinXP.
Comment 3 Carlos Garnacho 2013-07-10 13:18:36 UTC
I've attached a patch to that GTK+ bug, the fix hasn't been as straightforward, but has gotten rid of that calculation on screen coordinate space, and should work nicely from XP on.
Comment 4 Mikayla Hutchinson [MSFT] 2013-07-11 20:15:25 UTC
We have prepared a new build of GTK+ that contains this fix. To test it, please download https://mjhutchinson.com/files/temp/gtk-2.24.20-2013-07-11.zip and copy the directories it contains "C:\Program Files (x86)\GtkSharp\2.12". You can verify it is installed by checking that "Help->About->Show Details" shows "GTK 2.24.20".
Comment 5 Mikayla Hutchinson [MSFT] 2013-07-16 12:47:29 UTC
Seems to work correctly now.
Comment 6 Mikayla Hutchinson [MSFT] 2013-07-16 12:47:35 UTC
The new GTK+ binaries have been included in the GTK# 2.12.22 installer, which is now in the beta update channel and will roll out to stable after we're reasonably confident there are no regressions.

Please reopen if this happens with GTK+ 2.24.20.