Those functions are already implemented. The list of drawing functions
implemented is:
>>> filter(lambda x: x[:5]=='draw_', dir(gtk))
['draw_arc', 'draw_array', 'draw_gray_image', 'draw_line', 'draw_lines',
'draw_pixmap', 'draw_point', 'draw_points', 'draw_polygon',
'draw_rectangle', 'draw_rgb_32_image', 'draw_rgb_image', 'draw_segments',
'draw_string', 'draw_text']
>>>
About the only drawing primitive that is not supported at the moment is
the gdk_draw_image() one. The draw_array() one is a function for
displaying a numeric python array with GdkRGB.
The ignore file is a list of functions to not generate wrappers for
because a hand coded wrapper exists. This was necessary for those
functions as the wrapper generator I wrote does not handle GdkPoint arrays
for instance.
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
On Fri, 15 Oct 1999, Fred L. Drake, Jr. wrote:
>
> Are there plans to add any more of the gdk_draw_*() functions to the
> bindings? In particular, I'd like to see gdk_draw_lines(),
> gdk_draw_polygon(), and gdk_draw_segments(). I see these are listed
> in generate/gtk.ignore; is there a reason they're not included?
> I'd also like to suggest that gdk_draw_string() might need to use
> gdk_draw_text() internally; I don't think there's any guarantee that
> no font encodings use codepoint 0, so allowing a string with a null
> byte should be supported. I don't have an example, though, so this
> isn't a pressing issue.
> (For the interested: I'm working on a PIDDLE canvas that draws on a
> GtkDrawingArea, and takes care of double-buffering and resizing.)
>
>
> -Fred
>
> --
> Fred L. Drake, Jr. <[EMAIL PROTECTED]>
> Corporation for National Research Initiatives
> To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
>
To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
