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

Author Topic: (Very) small techdemo with sources (threaded OGL rendering)  (Read 16297 times)

0 Members and 1 Guest are viewing this topic.

l0calh05t

  • Full Member
  • ***
  • Posts: 200
    • View Profile
(Very) small techdemo with sources (threaded OGL rendering)
« Reply #15 on: July 31, 2009, 09:28:40 pm »
Quote from: "Laurent"
Quote
@Laurent would it be possible to use some code similar to this in sfml for better resize event prossesing?

I don't see what SFML could do with this code.


Nothing without switching to a separate render thread, which would probably make it quite beginner-unfriendly... (although maybe if the messages are polled automatically and forwarded... hrmm...)

klusark

  • Newbie
  • *
  • Posts: 45
    • View Profile
(Very) small techdemo with sources (threaded OGL rendering)
« Reply #16 on: July 31, 2009, 09:59:32 pm »
As long as the api stays the same, a hidden render thread could be added and beginner users would not notice. I am not sure if this is possible though. When I get a chance I will try to implement this.

Laurent

  • Administrator
  • Hero Member
  • *****
  • Posts: 32504
    • View Profile
    • SFML's website
    • Email
(Very) small techdemo with sources (threaded OGL rendering)
« Reply #17 on: July 31, 2009, 10:03:15 pm »
SFML is too low-level, it doesn't control anything about rendering. Objects are rendered when the user calls window.Draw. I couldn't even implement a rendering queue to be executed later / in another thread.

And besides, it sounds a little bit overkill...
Laurent Gomila - SFML developer

l0calh05t

  • Full Member
  • ***
  • Posts: 200
    • View Profile
(Very) small techdemo with sources (threaded OGL rendering)
« Reply #18 on: July 31, 2009, 10:09:31 pm »
Quote from: "Laurent"
SFML is too low-level, it doesn't control anything about rendering. Objects are rendered when the user calls window.Draw. I couldn't even implement a rendering queue to be executed later / in another thread.

And besides, it sounds a little bit overkill...


And inefficient. Better leave it as it is.
Suggestions about that crash issue are welcome though  :P