fd064863eb
Shut up many more gcc warnings.
2001-09-05 10:31:52 +00:00
77105a960b
The MacOS toolbox modules have acquired an _ in front of their name. Normal usage is through a wrapper module (without underscore) which lives in the Carbon package.
2001-08-23 13:51:46 +00:00
fa77e1a1b1
Lots more Carbon/Carbon.h includes, new UPP routine names, function prototypes. Most toolbox modules now compile, link and import in MacOSX-MachO python.
2001-05-22 21:56:42 +00:00
0e04eecdbf
First step in porting MacPython modules to OSX/unix: break all references between modules except for the obj_New() and obj_Convert() routines, the PyArg_Parse and Py_BuildValue helpers.
...
And these can now be vectored through glue routines (by defining USE_TOOLBOX_OBJECT_GLUE) which will do the necessary imports, whereupon the module's init routine will tell the glue routine about the real conversion routine address and everything is fine again.
2001-05-17 21:58:34 +00:00
9d8b96c850
pymactoolbox.h contains protoypes for all externally visible toolbox module
...
functions. Include it in stead of duplicating the declarations everywhere. Also
cleaned up toolbox module exports, and got rid of resNotFound error.
2000-07-14 22:16:45 +00:00
6dc8ce9108
Added PutPixMapBytes() and GetPixMapBytes() functions that allow getting at
...
pixmap data.
Added an as_GrafPort() method to be able to use a GWorld as argument to
routines that expect a GrafPort.
2000-03-03 16:03:06 +00:00
a4e6ae6667
Offscreen bitmap support, first stab. PixMaps are still treated as ordinary
...
handles, not fullblown python objects, and UpdateGWorld returns a new GWorld
object in stead of modifying the existing one.
1999-03-07 23:11:21 +00:00
Jack Jansen