Messages

1

Network / Re: Question about TcpSocket::receive()

« on: June 11, 2015, 04:59:29 pm »

Thank you, so you're saying that reading the TcpSocket buffer a single character at a time will work with a normal Selector.wait loop, awesome. No, I'm not actually reading a single character at a time.

2

Network / Question about TcpSocket::receive()

« on: June 10, 2015, 08:32:09 pm »

When I call receive() on a TcpSocket and there is more data available than the size of the buffer what happens to the rest of the data? Would I simple get it in a subsequent call of receive()? I'm using SFML 2.1 by the way and I know there is a partial status given for send() on Tcp now (in 2.3).

A small example case; lets suppose I use receive() to read a single character at a time, if I use a selector would selector.wait() trigger immediately, or would I have to stick selector.isready in a while loop?

3

Window / Window Not Opening

« on: January 31, 2012, 03:57:16 pm »

Yes i realize that just adding -s won't do it, but at least the tutorial should show me how, yet it doesn't. Also i blame the 100 topic starters for this problem (ATI graphics + SFML) but none of the replies that people give hold any relevance to a solution. Even Laurent (sp?) has been unable to provide a clear method to work around it, other than saying 'Statically Link It".

Sorry to the OP, but thus far you're just butting your head into a wall asking this question as no one can seem to answer it correctly and/or fully

4

Window / Window Not Opening

« on: January 30, 2012, 03:52:15 am »

This ATI graphics issue is very well known, very common, and has absolutely no workaround that a moderate programmer can do. Why is this?

I've looked into compiling SFML statically but it fails, i've tried rebuilding SFML statically, but it still fails, I've tried using the workarounds explained elsewhere, which kinda works, but still fails. Note; the workaround fails more often than not when using sf::String.

Please is there a possible fix, or an easy way to link against SFML statically that actually works? Just adding -s after the -lsfml-XXX doesn't want to work.

There are probably around one-hundred (100) topics showing this same error, yet no one can answer their questions or provide a way to fix their problems.

This is all assuming SFML 1.6 as it says that's the 'current' version, Once SFML 2.0 is considered current most will use 1.6

5

General / sf::ConsoleWindow

« on: May 08, 2011, 09:39:07 pm »

Pretty much just a standard console with cin/cout/cerr

6

General / sf::ConsoleWindow

« on: May 07, 2011, 12:42:15 am »

I mean if one window is closed but you still do stuff with it like events?

7

General / sf::ConsoleWindow

« on: May 06, 2011, 12:49:11 am »

Hmm,  but wouldn't it crash when the console is closed but the game window isn't?

8

General / sf::ConsoleWindow

« on: May 05, 2011, 05:54:55 am »

I guess I'm lost on how to structure the loop for it really.

9

General / sf::ConsoleWindow

« on: May 04, 2011, 06:35:52 am »

But just setting it up is where im drawing a blank.

I'm pretty skilled with the actual console, just trying to implement my own isn't lining up thought wise

10

General / sf::ConsoleWindow

« on: May 04, 2011, 03:56:36 am »

Is it remotely possible to make a console window in an SFML window? More specifically sf::RenderWindow.

It would only need functions similar to std::cout, std::cin, std::getline.

It would mean that cin wouldn't 'freeze' the window like it does in the console.

I've been trying to make one, but it's just in my range of skills.

PS: Is this the right place for this topic?