On Mon, 2008-04-14 at 12:11 -0700, Blake Ramsdell wrote: > On Thu, Apr 10, 2008 at 12:20 AM, Emmanuele Bassi <[EMAIL PROTECTED]> wrote: > > I should also strongly point out that, by using trunk, you're tracking a > > highly unstable development branch. so, if something breaks, you get to > > keep both the pieces. > > Or I can glue them back together if you want. Like PyClutter wants the > stage parameter for redraw. I can fix this by either requiring that > redraw take a stage parameter or make redraw a member of the stage > object (though I suspect you might want to refactor the C name to be > clutter_stage_redraw and move it to clutter_stage.h in that case).
clutter_redraw() should not be used by applications - every application code should use the ClutterActor::queue_redraw() method instead. in any case, and after the experience of 0.2, 0.4 and 0.6, making the bindings track trunk is an incredibly bad idea; the bindings will have to wait until the API in trunk enters a "slushy" state, with a semi-frozen API. unless, obviously, people are willing to keep submitting patches when trunk changes. ciao, Emmanuele. -- Emmanuele Bassi, OpenedHand Ltd. Unit R, Homesdale Business Centre 216-218 Homesdale Rd., Bromley - BR12QZ http://www.o-hand.com -- To unsubscribe send a mail to [EMAIL PROTECTED]
