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.
If you load this sample in C6:
you don't get all of the UI. Something is broken it appears. Regression from C5.
[10:14 AM] Kevin Munster ☠: I did just find something… so the first load isn’t displaying subview loaded from sub `.xibs` however the second time it is issued, the view is displaying. On the outline views no text is being displayed but the “items” are there. It’s like the text and icons are transparent. Still looking for the simplest sample.
Chris, so the simplest one that is broken is MacImages and it is limited to the Outline view, something has changed there and since pretty much all the samples are built off of the outline, almost all are broken. In one of my samples I did get this message in the output after I ended the app:
```MacOutlines[30774:8373095] *** NSOutlineView data source (<MacOutlines_ProductOutlineDataSource: 0x10e016fe0>) does not implement outlineView:persistentObjectForItem:
It appears to be an issue with members of the outline view delegate not being called.
Possibly related to e00c49c0b7679b9aaa62584674d99d3ac2094b4b.
Debugging in process.
So in that hash for all the methods removed, except one, if you override in a sample and check base symbol, you will see the export tag. That is except this one:
- [Lion, Export ("outlineView:viewForTableColumn:item:")]
- NSView ViewForTableColumn (NSOutlineView outlineView, NSTableColumn tableColumn, NSObject item);
The problem appears to be that we had a different binding for that one as well:
[Export ("outlineView:viewForTableColumn:item:"), NoDefaultValue]
NSView GetView (NSOutlineView outlineView, NSTableColumn tableColumn, NSObject item);
and the patch obsoleted one and kept the other. However, that breaks every single person who was calling the other one. This is unacceptable. Our choices are:
- somehow fix this
- Remove ViewForTableColumn completely and make it a breaking change.
What we have right now is worse than both of those options.
Fixed in master / 9a385a67a378e04cee85cd620a70511d95076907
I have checked Xamarin Mac "MacOutlines" samples with Master build
and I am not able to run the sample application due to the runtime exception. I have filed the following bug for the same: https://bugzilla.xamarin.com/show_bug.cgi?id=35398
I am unable to verify this issue due to above issue. I will verify this issue when bug 35398 will get resolved.
Bah. As this commit shows:
Author: Chris Hamons <firstname.lastname@example.org>
Date: Fri Oct 30 16:59:19 2015 -0400
Remove ViewForTableColumn since Obsolete (string, bool) does not do what you think
- Fun fact, if you obsolete a virtual method that is never called in your code (say binding) it is a warning, NOT an error.
- So, what can we do but nuking it? If you override "wrong" one, your app just stops working.
My first fix was wrong. So let's nuke it for orbit :(
Sample Info: mac-samples1e20a0d29145ec19c031fa611c7225e1998f6d89
I have checked this issue with the Cycle 6 build
xamarin.mac-126.96.36.199_63c58d9d2e557031edb410f22057b2ca8445a6f8 and observed that this issue does not exist with this build. Now I am able to build and run the application
successfully, and getting the expected behavior as mentioned in the bug description i.e. I am t getting all of the UI.
This fix has been merged in release branch and working fine, hence I am closing this issue.