Messages

1

Graphics / Re: Are SFML shapes suitable for collision detection?

« on: July 29, 2013, 04:52:17 pm »

Sorry about the delayed response. I decided to take eXpl0it3r's approach and implement my own shapes with a sf:Transform and it's working out well. Thanks everyone for your input.

2

Graphics / Re: Are SFML shapes suitable for collision detection?

« on: July 22, 2013, 07:50:05 pm »

Oh yeah. Well I should have said I am thinking about non axis aligned stuff. So the rotation, transforms, and get-bounds functions of the sf::shapes would be super useful to have already done for me.

Actually I am probably worrying over nothing since the shapes wouldn't even have some of those functions if they weren't intended to be used for math.

3

Graphics / [SOLVED] Are SFML shapes suitable for collision detection?

« on: July 22, 2013, 07:30:12 pm »

Hello,

I want to use SFML shapes for collision detection to save me some work and for this purpose I won't be using them for rendering (except for maybe debugging). Since I don't know much about OpenGL or the underlying code I am just wondering if they are lightweight enough for this purpose.

4

Python / Python binding buggy?

« on: December 24, 2010, 08:33:42 pm »

Okay I tried compiling with MinGW 4.5 and I don't get the crash errors anymore but I do still get the one error from the image functions.

5

Python / Python binding buggy?

« on: December 24, 2010, 02:03:00 pm »

I am getting exactly the same errors as posted here. I'm running vista32 and python 2.7 32bit. I've tried the precompiled binaries and compiling them myself with MinGW 4.4.1 with the same results.

Whenever python tries to dispose of a sf window it will immediately crash the interpreter without an error.

Code: [Select]

from PySFML import sf
import gc

win = sf.Window()
del win        # Nothing
gc.collect()   # Crash

I can run the worms example but it crashes past the menu selection.

I don't know if it's related but I also get errors using some of the image functions. Specifically, sf.Image.Copy() and sf.Image.Create() will both produce this error:

Code: [Select]

Traceback (most recent call last):
 File "<stdin>", line 1, in <module>
SystemError: ..\Python\getargs.c:1424: bad argument to internal function

6

System / Resource and ResourcePtr

« on: August 03, 2009, 06:41:10 pm »

Thank you. That answered my question.  

7

System / Resource and ResourcePtr

« on: August 03, 2009, 06:05:36 pm »

Hello I'm new to SFML and C++ and I'm trying to make my own resource manager to get some experience and decided to use the built-in Resource and ResourcePtr classes.

After struggling a bit I realized that whenever you try to access the resource of a pointer it will always return a constant of that resource. Now, const correctness is something I usually don't bother with so I am a little lost.

How can you use resource pointers if it always returns a constant? Are mutators impossible in this situation?

It seems like a really useful feature but a little contrained. I guess if I have to I'll do my own reference counting with raw pointers or use another library, but I'd really like to use the built-in features if I could.