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 - blue_prawn

Pages: [1]
1
Network / sf::IpAddress::getPublicAddress(): timeout parameter ignored
« on: October 31, 2019, 11:38:30 pm »
Hi,
Yesterday sfml-dev.org was down, and so www.sfml-dev.org/ip-provider.php was not accessible.
Then I noticed that the timeout parameter of sf::IpAddress::getPublicAddress() is ignored.
The functions was not returning before a long time, I don't remember how long, but maybe something like 3 minutes even when the timeout was set on 3 secondes.

Should I fill an issue?

2
Network / is "sf::SocketSelector .wait()" required?
« on: October 31, 2019, 10:53:23 pm »
Hi,
I'm new to network programming, and I have a question related to the use of the .wait() method from a sf::SocketSelector object in this example:
https://www.sfml-dev.org/documentation/2.5.1/classsf_1_1SocketSelector.php

I read in the documentation that wait() is blocking, so I was wondering if it's possible to not call this function, and call directly .isReady() on my sockets.
Being a beginner with network programming and also with threads/concurrent/asynchrone programming I was wondering if I could start with a single thread and avoid blocking functions like wait()?

3
Hi,

It's about this page:
http://www.sfml-dev.org/download/bindings.php

The correct case for OCaml is OCaml (not Ocaml).

Thanks

4
General / Re: references to keep between different objects
« on: June 10, 2012, 06:43:09 pm »
Thanks a lot Laurent !
I appreciate in particular how fast you answer to questions.

5
General / references to keep between different objects
« on: June 10, 2012, 04:51:57 pm »
Hi,

I'm the author of the ocaml-sfml bindings.
OCaml is a garbage collected language, so I need to know the precise relationships between objects that interact together to know which should keep a reference alive around and which don't have to.

For SFML-1.6 Laurent gave me these informations:

- Sound  should keep a reference on its SoundBuffer
- String should keep a reference on its Font
- Sprite should keep a reference on its Image
- PostFx should keep references on all its Images given with SetTexture
- Window should keep a reference on its Input
- RenderWindow should keep a reference on its Input
- RenderWindow should keep a reference on its CurrentView and its DefaultView

So could someone help me to update and complete these informations for SFML-2.0?

When object A uses object B, does B have to stay arround or may it be deleted?

- Sound  should keep a reference on its SoundBuffer
- String should keep a reference on its Font
?? Texture ?(should | don't have to)? keep a reference on its Image ??
?? Sprite ?(should | don't have to)? keep a reference on its Texture ??
- RenderWindow should keep a reference on its CurrentView and its DefaultView
?? Shape <=> Texture ??
?? SocketSelector <=> Socket ??
?? Socket <=> SocketSelector ??
?? Shader ??

... others ???

Pages: [1]
anything