[MonoTouch] Still IntPtr Constructor issues

[Dean Cleaver]

Is there a reason why you don't want to implement the IntPtr constructor? I have in all of my superclasses as I have experienced disposal/GC problems without it.

Dino

From: monotouch-bounces at lists.ximian.com [mailto:monotouch-bounces at lists.ximian.com] On Behalf Of Rene Ruppert
Sent: Wednesday, December 07, 2011 1:55 PM
To: monotouch at lists.ximian.com
Subject: [MonoTouch] Still IntPtr Constructor issues

Hi,

I'm still struggling with the IntPtr Constructor issue I started on SO.
I got a bit further meanwhile.

The case is: I'm subclassing UITableViewCell and do not provide the IntPtr:ctor.

By adding the ctor and breaking in there I figured out what ObjC wants my class to do: it is calling void SetSelected ( bool selected, bool animated ).

This means "something" wants to select my cell. I looked through my code and found exactly ONE place where I call SelectRow(). I commented that out and STILL it goes through the ctor and to SetSelected().

What are my options now? Does UITableViewCell maybe always require the IntPtr ctor?
What could possibly still select a row in a UITableView besides SelectRow()?

René

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/monotouch/attachments/20111207/b4791891/attachment.html