Elysian Shadows

I'm making a map editor for a 2D RPG, and I'm using SDL_Rects for collision, so I can do custom collision for pretty much whatever I want. In the editor, you draw them with the Middle Mouse Button... For some reason, whenever I scroll away from where I drew the Rectangle... when I come back 1/20th of the time, the rectangle has resized itself, or completely deleted itself. Does anyone know of/ has had any problems relating to this, with rectangles randomly deciding to give themselves a haircut?

I had a similar problem once before, I believe I was colliding some SDL rects really fast into a wall, and shrank to half their size, but in all honesty, I don't know how I fixed it, and I don't have a clue what I did in the first place (but it's never happened again)

it seemed that any rects with a w/h that ends up past 1024 or 768 respectively, cuts itself down to size to fit into that, or into the screen. After like a half hour of researching through the docs, I ended up making my own class. It works perfectly now.

It's been a looong while since I've used SDL...But I do seem to recall having a similar problem. From what I understood, you cannot move a rect offscreen...Ever. You'd be blitting off the surface. So SDL simply resizes the rect to give the appearance that it's going off the screen--basically it catches your fuckup gracefully.

Though there's always the fat chance that I don't remember correctly, am an idiot, etc, so don't quote me on this one. ;p

Have you tried googling it?

ibly31 wrote:it seemed that any rects with a w/h that ends up past 1024 or 768 respectively, cuts itself down to size to fit into that, or into the screen. After like a half hour of researching through the docs, I ended up making my own class. It works perfectly now.

Code: Select all

class rect {
Public:
int x,y,w,h
};

It works now. But thanks, that's pretty much what I guessed except a little more detailed. I'm using Visual basic to make a NPC editor, I'm suprised at how EASy it is!

Haha, true dat.

Start building...But without a framework.

That's something we'd probably make peter pull out of his asshole.

Yes, things are always easier in BASIC languages for that reasoning...Until you begin trying to solve some of the more complex problems. Then you end up running into language limitations and would have been better off starting off in C++ or another powerful, lower-level language.

Just nitpicking a litte; since you're not using any class "things": Don't start a holy war, please.

Scoody wrote:Just nitpicking a litte; since you're not using any class "things":

Code: Select all

struct rect {
  int x,y,w,h;
};

Don't start a holy war, please.

BTW, the struct and class keywords do EXACTLY the same thing in C++. Only difference is structs are public by default where as classes are private.

dandymcgee wrote: BTW, the struct and class keywords do EXACTLY the same thing in C++. Only difference is structs are public by default where as classes are private.

As I said, only nitpicking.

Scoody wrote:As I said, only nitpicking.

Same.