Two methods of rendering custom displayables

[Eliont]

Hello and good time of day.

What difference between method #1 and method #2 ?:

Code: Select all

    def render(self, width, height, st, at):    
      # 1 
      render = renpy.Render(self.xsize, self.ysize)
      render.place(self.sprite)
      # renpy.redraw(self, 0.0)
      
      # 2
      # child_render = renpy.render(self.sprite, width, height, st, at)
      # self.width, self.height = child_render.get_size()
      # render = renpy.Render(self.width, self.height)
      # render.blit(child_render, (0, 0))

      return render

[gas]

The subject is debatable as we must understand the code logic applied by the core designer.
To my understanding of the thing, the second was implemented to open for users the chance of having both a generic Displayable that control the behaviour of the object, and a child of it (the rendered image), creating the base for the UDD.

[Eliont]

Btw, is there somewhere extensive guide for UDD (ever if it paid) ?
Not the "proof of concept" that resides in https://www.renpy.org/doc/html/udd.html

[zmook]

I've seen a lot of references to "UDD" but can't find a definition. Is it the same thing as "Creator-Defined Displayable"? ("User-Defined"?)

[gas]

I've seen a lot of references to "UDD" but can't find a definition. Is it the same thing as "Creator-Defined Displayable"? ("User-Defined"?)

I dunno why, but is the same thing that changed name thru time. Probably as by "user" someone meant the one playing the game, and "creator" the one that's doing it.

====
As for the OP: a CDD/UDD is nothing but a PyGame child class, so to use it the best way is to learn how PyGame work.
You don't have to render directly or create a controller for state, but once you know how to manipulate a PyGame object, you own the proper know how.
Is a vast subject, and not really well documented as Renpy wasn't mean to use it a lot.