Welcome, Guest. Please login or register. Did you miss your activation email?

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - alienGhost

Pages: [1]
1
General / Text Output in OpenGL ?
« on: November 21, 2011, 05:57:16 pm »
thanks Laurent. for some reason I believed that you could only use a RenderWindow with SFML draw commands. I will try switching my display setup to use it.

2
General / Text Output in OpenGL ?
« on: November 20, 2011, 11:29:33 pm »
hey, that's the problem. i am using OpenGL directly for drawing and shaders (not SFML). but I would still like to use sfml's font facilities, somehow.

i thought maybe overloading sf::Text's Render method. not sure.

EDIT: oh, im using SFML 2 - just incase

3
General / Text Output in OpenGL ?
« on: November 20, 2011, 07:30:34 am »
Hi,

I'm using SFML as a GLUT replacement for OpenGL/GLSL.

I have an sf::Window for my output and would like to use SFML to output text. It doesn't seem possible, or am I missing something?

I notice in the sf::Text object has a virtual method called Render. I've not looked very deep, but would it be possible to derive a class from sf::Text and implement drawing to an sf::Window?

SFML really needs to support sf::Window output if possible. It's a killer-app for people wanting to ditch stuff like GLUT and freeGLUT.

4
General / Statically Linking Issues [not quite resolved]
« on: June 28, 2010, 01:22:31 pm »
aha! i think i just forgot to add "-static" static binding as linker option. seems to be working ok now.  :oops:

5
General / Statically Linking Issues [not quite resolved]
« on: June 28, 2010, 12:24:35 pm »
i'm getting very similar errors when attempting to compile static build using the gcc 4.4 mingw build from the tutorial and SFML 1.6 (for mingw). did anyone figure this out?

6
Feature requests / Greater Pixel Access in sf::Image
« on: May 13, 2010, 07:55:12 pm »
Quote from: "Laurent"
Nothing changed in SFML 1.6, but SFML 2.0 will probably soon have a much better API for dealing with pixels. It already implements a new Image::UpdatePixels function that avoids copying the pixels to the Image cache; instead they go straight to the video memory.

So, currently the best solution is to use SFML 2.0, an external raw array of pixels, and Image::UpdatePixels whenever you want to sync the image with it.

There's currently no similar option in the audio module, to avoid the internal copy of sound samples when updating a sf::SoundBuffer.


thank you very much Laurant! the new UpdatePixels in v2 sounds a lot more efficient...and updating each frame should be no problem for graphic works.

as for audio, this i think will be my problem in both SFML and SDL as i need access  realtime audio stream for dynamic sound manipulation.

i'm thinking i can hopefully use sfml in combination with something like RtAudio library http://www.music.mcgill.ca/~gary/rtaudio/.

bah, Processing and its 3rd party libs made this so much easier! I have a lot to take in learn.

thank you again!

7
Feature requests / Greater Pixel Access in sf::Image
« on: May 13, 2010, 02:29:00 pm »
Quote from: "Laurent"
Ok, fair enough :)

In the future I'll try to provide faster and more direct access to pixels. I think there is some room for improvement there.


Hi...I'm currently evaluating the potential of using either SDL or SMFL for a university project. I have been using java/Processing for my first year for image/audio convolution and general DSP techniques - we will now be moving on to C++ and we have been asked to research APIs to use for similar work in year 2, during our current holiday.

I need relatively painless/fast access to the pixel buffer. So far I like the look of SFML more, but because my project will involve direct access to pixels, SDL seems to have bonus points for this historically.

I can see SFML 1.6 has been released, has there been any improvements on direct pixel access in this new release?

thank you for any advice!

EDIT: I'm sorry for making this post long but additionally: does anyone have a good sense of which API (SDL or SFML) is better for fastest/simple access to raw data (audio/pixel) _overal_. in other words, which would be more suited to DSP techniques. It's very hard for a noivce like me to tell immediately, without wasting a lot of time testing different APIs...so if anyone has any hints on this.

Thank you!

Pages: [1]
anything