On 02/03/2015 04:20 PM, Brian wrote:
Threading SDL 2.03 is not particularly difficult if you observe the rules
Nonetheless you need to take a lot of care when implementing any
communication between multiple "Windows".
-Michael
___
fpc-pascal mailli
Threading SDL 2.03 is not particularly difficult if you observe the rules
that a texture/renderer must reside in the same thread that created the
window and (it appears) there is only one event (which as you mentioned
makes sense) , and in my case the event handler is in a thread.
SDL 2.03 has so
On 02/02/2015 03:54 PM, Brian wrote:
When the event handler (only one handler) is put in a thread , the event can
be detected from different windows , those created in the thread and those
created in the main thread (program) , by using SDL_GetWindowID() to get the
identify of a window (WindowID)
It appears (though I can't find any documentation / forums that actually
states this) that SDL 2.03 only allows one event handler.
When the event handler (only one handler) is put in a thread , the event can
be detected from different windows , those created in the thread and those
created in the
I currently have an application running under Ubuntu 14.04 using SDL 2.03 and
have a few questions .
Currently the window / rendering / event handler are running in a thread ,
not the main program. This works fine as long as the window is initiated
(created) in the thread , and the rendering / ev
