Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
This also shows up when using WIMP so it appears to be a GTK issue, not a theme issue.
Can we please prioritize this? it s a serious regression from GTK 2.16.x.
*** Bug 11080 has been marked as a duplicate of this bug. ***
Created attachment 3627 [details]
So, I tried to see where the issue was coming from, and ended up by commenting these two lines in PropertyGridTable.cs:
//ctx.Rectangle (0, y, dividerX, h + PropertyTopBottomPadding*2);
ctx.MoveTo (x, y + PropertyTopBottomPadding);
Once those lines are commented, the result is as seen in the screenshot attached; the text in the fields is shown, but the right label overlaps on top of the field text.
Now, the original code looks right to me, so this really seems to be an issue with the Pango/Cairo layout handling...
I have a theory but can't test it because I don't have windows:
PropertyGridTable.cs (Draw) uses ShowLayout on a cairo context to draw
the property's name, and then calls
PropertyEditorCell.cs (Render) which uses gdk_draw_layout().
I would guess that mixing these two ways of drawing strings doesn't
work well on Windows. Without fixing the actual bug, we could perhaps
work around it by simply using ShowLayout in PropertyEditorCell too.
*** Bug 11692 has been marked as a duplicate of this bug. ***
If it helps, the problem for me only exists when the pad is docked. If un-docked as a floating window, the fields render fine.
Created attachment 3805 [details]
Created attachment 3806 [details]
The previous two patches for monodevelop avoid the issue with the cairo+pango mix. I've tried them under win32 and they do work properly.
Regarding the actual cairo+pango issue, didn't get much info yet.
Reviewed, applied, tested and pushed. Thanks!
Let's forget about the upstream issue for now, not worth fixing mixed Cairo/GDK drawing issues IMO. I found a few with the latest Cairo on Mac and similarly fixed them by porting the text rendering to Cairo.
For the record, this is also a sort of undeprecation that will make
porting to GTK+ 3.x easier.
Agreed. A while back I started migrating Gdk code whenever I get the chance.