{"shas":[["a710579abb822ddb8f1ed22fe84e56c9b480229f","dc1d736ff5996b193c74895bd3f20a7274a2af8a@gmail.com","Fix build, by adding CoreMedia library","Regan Sarwas"],["e341fc6645e3503cb3e8d477b3af8db814fe02fe","dc1d736ff5996b193c74895bd3f20a7274a2af8a@gmail.com","I think I finally understand the Drag/Drop classes for monomac, and have provided\ndragging.patch (for monomac) with the appropriate changes to appkit.cs.  In essence\nthe messages that are sent to delegates that might respond to 'drag events' are\nsent an object that implements NSDraggingInfo.  NSDraggingInfo is a protocol, but\nimplementing this as a [Model] does not work because this object is not created by\nclients, and the runtime cannot cast the actual object created by appkit to the\nC# class.\n\nDrag and Drop Programming Topics for Cocoa mentions that the system\ncreates an undocumented NSDragDestination object which implements NSDraggingInfo.\n\nSince the docs refer to NSDraggingInfo and not NSDragDestination, and since\nNSDraggingInfo is a more descriptive name, it is used in appkit.cs, and the Name\nattribute is used to register NSDraggingInfo to NSDragDestination.  I tested this\nwith NSDraggingDestination and NSBrowserDelegate, and all seems well.\n\nIt could be improved by privatizing the constructors for NSDraggingInfo.","Regan Sarwas"],["c54215bf6633d8b5ee5d7e5911aace6c8fceb4ce","dc1d736ff5996b193c74895bd3f20a7274a2af8a@gmail.com","Removes some warnings from the samples","Regan Sarwas"]],"repo":"mono/monomac","actor":"migueldeicaza","ref":"refs/heads/master","size":3,"head":"c54215bf6633d8b5ee5d7e5911aace6c8fceb4ce","actor_gravatar":"3a9106e0c085d9a856588c454894d66b","push_id":26680822}