ultramailman

char isn't guranteed to be one byte

I remember from somewhere that char is always one byte. Then short <= int <= long <= long long.
 
If you are worrying about this, why not use long or long long instead of int? They might be bigger than int.
 

int endianess(void)
{
        union{
                long long l;
                char c[sizeof(long long)];
        } n = {1};
        return n.c[0];
}

Also check out stdint.h, if the compiler you use supports it.

//quit the program
Quit == true;

 

This part needs some fixing.

Well, no one is stopping you (except yourself). : /

You are not using the variable WHITE anywhere though. If you want the surface to be white, you have to call fill on DISPLAY, then call flip.

 

Each file will have a separate, distinct pygame object (or whatever it is).

 

I think multiple imports of the same module will only have the effect of one import. The first will add the module object to a dict, and any other times it will just do a look up.

Ah, good for you. What made you decide to do this?

Have you used it? Which one do you recommend? Why?

I have not used GTK+ before. In fact, I have no experience with GUI programming. However, I have noticed a majority of programs on linux uses GTK+ or QT. Qt is C++, so that leaves GTK+. And like what Bearhugger said, GIMP is an example of a program that uses GTK+. Take a look at that to see if you like it.

Here you go
http://en.wikipedia.org/wiki/List_of_widget_toolkits#Based_on_C_.28including_bindings_to_other_languages.29

GTK is pretty common on linux, so maybe that?

fseek can be used to set the position of an open file stream, but it is only portable if your file is read and written in binary mode.

 

Is this what you mean?

Ok, now I see what you mean. The array you are looking for is in the Grid class. You don't see it in the Board class because Grid has it. Is the Grid class available to you? You will have to see which methods of the Grid class allows you to change the array.

If you mean writing the contents of a piece array into the board array, I think it should happen only when the pieces settles down, and not when it is still moving. So I don't think it belongs in the moveLeft method, unless I am misunderstanding you again.

I guess I am confused again. When you say "putting a piece inside the board", do you mean when a new pieces comes into the view at the top? Or do you mean when the piece finally settles down and becomes a part of the board landscape?

Oh I see what you mean, after thinking about how I would make a tetris clone.

I suppose I would keep the position of the shape that is currently dropping down, and not write the shape array into the content array until the shape hits bottom and becomes part of the unmoving blocks.

You can try checking for collision after the movement is done. If there is a collision, then undo the move. I think that will work for all three directions.

also,

for(i = 0; i < SIZE; i++)
    {
    array[i] = 0 //<- missing a semicolon here!
    }

Let's say we want 60 fps. 60 fps means 60 frames per 1000 milliseconds. That's around 16 or 17 milliseconds of time to update and render. If updating and rendering takes less than 16 milliseconds, then wait the remaining time to keep fps near 60.

Thats the gist of it. For further reading, check out an article called "Fix your Timestep!". It's more advanced, but don't let it confuse you.