I see the point, but SDL seems to be pretty stable isn’t it? Only two versions are reported on their website (1.2 and 2.0). Maybe it would be better to directly talk to SDL. Just wondering...
Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Apr 20, 2015, at 4:18 AM, stepharo <steph...@free.fr> wrote: > > Alex > Just to make sure we are clear on this: > pay attention NOBODY should directly use SDL. > OSWindow is the API, SDL is a BACKEND. > > Athens is the API, CAIRO a BACKEND > > Stef > > Le 20/4/15 02:57, Alexandre Bergel a écrit : >> Hi Matthieu, >> >> This is important: Binding SDL with Pharo will help Roassal to get better. >> Please, let us know how it goes >> >> Alexandre >> >> >>> On Apr 9, 2015, at 12:54 PM, Matthieu Lacaton <matthieu.laca...@gmail.com> >>> wrote: >>> >>> Hello everyone, >>> >>> I tried to use the SDL2 binding to Pharo to create a very basic 2D >>> application (just some sprites and events) and it worked great. >>> The issue I have is that when I start my application, as long as I have an >>> active SDL window, I can't use my Pharo image anymore (it freezes). >>> To solve this problem I tried opening my application in another thread by >>> doing so : >>> [ (MyApplication new) start. ] forkAt: Processor lowestPriority. (If I >>> don't chose a low priority it changes nothing) >>> >>> The problem is that even if it kind of works, it is really slow and it >>> slows my whole operating system as well (I use windows XP) >>> >>> How can I fork more efficiently or open a SDL window without losing control >>> of my image ? >>> >>> Thanks, >>> >>> Matthieu > >
