[Mono-osx] [MonoMac] Misc Patches
rsarwas at gmail.com
Wed Jan 19 01:47:33 EST 2011
On Tue, Jan 18, 2011 at 10:22 AM, Miguel de Icaza <miguel at novell.com> wrote:
> Hello Regan,
> > 1) First off the samples do not build on a clean clone of github.
> > Samples.patch fixes that.
> > 2) NSAffineTransform: Added a missing struct, and finished the bindings
> > this class. In the mac libraries, part of this class is defined in
> > Foundation, and part in Appkit (as extension methods). Since this class
> > only available in OS X, and it all ends up in monomac.dll, I saw no need
> > separate the class. let me know if it should be otherwise.
> Is there a reason why we cant just use the existing CGAffineTransform
> class defined in CoreGraphics instead? It already has a bunch of
> useful methods defined, and we could unify some code.
Good catch. I didn't use it, because I didn't see it. Disregard that
patch, and I'll send you something tomorrow.
> > 3) NSBezierPath: Added manual bindings to complete the class. I
> > with the packedGlyph array, and decided it was best to expose this as a
> > "black box" IntPtr. It probably won't be needed from most user code, and
> > you want a packed array (as I do in my sample), you are going to get it
> > an IntPtr from some other cocoa object. I have verified it works
> > I will provide docs for the manual bindings shortly.
> Is there a reason to drop the CreateBezierPath() method? Does the
> plain constructor just work?
> Yes - I did some testing to confirm, and AFAIK, [NSBezier BezierPath] is a
"short cut" for [[NSBezier alloc] init], and provides some symmetry with the
other Bezier constructors in cocoa. In C# it is just redundant (and
therefore confusing), which is why I suggest removing it.
> I applied the Bezier patch.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-osx