Is img_mii created each time GRRLIB_DrawMii is called? Is it created with GRRLIB_CreateEmptyTexture?

Just an idea like that. I think that img_mii is problem because it writes the new image over the old one.

Try to draw a rectangle the size of img_mii just after GRRLIB_CompoStart(). Before you draw anything else to test clearing the texture.

A better idea would be to use GRRLIB_ClearTex(img_mii) as the first line of GRRLIB_DrawMii.

mdbrim wrote:

yeah but if it clears the texture, how do i end up drawing it?

What I had in mind was something like this:

void GRRLIB_DrawMii(const f32 xpos, const f32 ypos, Mii mii, const f32 degrees, const f32 scaleX, const f32 scaleY, const u32 color, const int type) {
    GRRLIB_ClearTex(img_mii); // Clear previous version of img_mii
    GRRLIB_CompoStart();
        Here go my 20+ drawtile events that build the mii.
    GRRLIB_CompoEnd(0, 0, img_mii);

    GRRLIB_DrawImg(xpos, ypos, img_mii, degrees, scaleX, scaleY, color); // Draw the Mii on the screen
}

Would it be better to have a function like GRRLIB_CreateMiiTexture? It would a lot faster to use, no need to generate the texture each time. People will only need to call GRRLIB_DrawImg with there Mii texture.

Sorry I don't understand.
Calling this:
GRRLIB_DrawMii(20, 30, miis[2], 0, 1, 1, 0xFFFFFFFF, 1);
Will draw a texture on the screen. Once it's on the screen we don't care about clearing or not the texture! So we could call this without any problems:
GRRLIB_DrawMii(20, 70, miis[5], 0, 1, 1, 0xFFFFFFFF, 1);

Maybe you should paste more code.

i think mdbrim is right,
GRRLIB_DrawMii will compo start, draw shit, compo end, and draw it.
so each time you will call GRRLIB_DrawMii the screen will be cleared, then a mii will be draw.

i think you should have only this function
GRRLIB_PreCalcMii (compo start, draw shit, compo end)

Then draw the precalulated mii many times you want using GRRLIB_DrawImg

but i think all this already explained by crayon in an upper message.

just create a new empty texture when you need one

i guess i can pass a texture name into GRRLIB_DrawMii and always clear and create... that way when i do another mii, i just pass a different texture name.  Me goes to try!

ok progress!

void GRRLIB_BuildMii(Mii mii, const int type, GRRLIB_texImg* tex) {

        GRRLIB_ClearTex(tex);
        GRRLIB_CompoStart();
           build up mii number "mii" with some options "type"
        GRRLIB_CompoEnd(200, 160, tex);
}

int main() {

   while(1) {
      GRRLIB_BuildMii(1, 1, img_mii1);
      GRRLIB_BuildMii(2, 1, img_mii2);

      GRRLIB_DrawImg(0, 10, img_mii1, 0, 1, 1, 0xFFFFFFFF);
      GRRLIB_DrawImg(0, 200, img_mii2, 0, 1, 1, 0xFFFFFFFF);

problem is, i still need to know how many max mii's i'd allow so i can do all the "static GRRLIB_TexImg* img_mii1" and "img_mii1=create empty texture" stuff.

But it's a step closer!

Last edited by mdbrim (2010-03-12 07:55:59)

i'm not getting the code dump anymore since i took the img_mii = create new texture out of the GRRLIB_BuildMii function.

BUt it was dumping when i had tex = GRRLIB_CreateNewTexture(200, 160); underneath the ClearTex(tex);


now i have img_mii1 =GRRLIB_CreateNewTexture(200, 160); up where the rest of textures are done.

but i also have to have img_mii2, img_mii3, etc.

It works, it would just be nice not to have to create 20 img_miiX = GRRLIB_Create new texture... what if the programer wanted to put 100miis... he'd need a 100 of those lines.  Not THAT big a deal... but not the cleanest

well i won't be able to release it until i figure this part out...

If yes, I don't see the point, if the opposite I don't see point either.

yeah, the create new texture shouldn't be in there, i just thought i would be able to create textures on the fly with that code.

You would use malloc with the total number of Miis? I'll be trolling around irc throughout the day so maybe i'll see if i can get you to show me what you mean.

http://pastebin.com/qrDSeYr0

you can see lines 52 and 53
and lines 119 and 120

that's what i'm trying to aviod... having 20 lines of those if i want 20 mii's on screen at once.

Last edited by mdbrim (2010-03-12 15:49:58)

the reason the GRRLIB_BuildMii is in the loop is because i pass a variable that defines mood / animation.

So it updates the Mii with a happy face or sad face or closed eyes every random seconds for blinking.

Static Mii's that don't need to blink or change facial expression can be outside the loop... i just had those in there for a blinking test.



I'll try out that loop... thanks!

What about making a Class/Struct, and have the Draw function and the texture in that?
Then you can have an array of those objects.

You can then make a subroutine which loops trough all the objects and calls their Draw functions.