From: Joschka B. <jbo...@un...> - 2007-06-04 11:05:41
|
Hi Yuan, Yuan Xu wrote: > Hi Joschka, > > >> >> .... If the >> >> application is too busy for SDL to create appropriate events, do you >> >> think it would make sense to have an other application ("referee") >> that >> >> connects to the server as a monitor and sends commands using the >> trainer >> >> protocol? This way we could make the game kick of and do drop ball at >> >> least... >> >> > > I found this in http://www.libsdl.org/intro.en/whatplatforms.html > > "Linux and BeOS support the SDL_INIT_EVENTTHREAD flag which, when > passed to SDL_Init(), asks the event loop to run asynchronously in > another thread. This is useful for color cursors that respond even > when the application is busy." > > But initializing SDL with SDL_INIT_EVENTTHREAD can not get clear > effort ;-( It sounded very helpful, but my tests so far also didn't get a clear result. In fact, the input can be best controlled in single-thread mode without using the SDL_INIT_EVENTTHREAD mode for me so far. By the way, I think I'll write an email to the list today, asking for feedback on the timer. It's important to hear the teams' experience before we make a decision for Atlanta, I think. > > If the monitor and server run on one machine, it seems OK. > But I have some problems while connecting the monitor via the net. > If there is no agent, the monitor works OK. > If one agent connected, and the full scene message is received, but > the prefix size of message can not read correctly! > It reminds me what happened in the agentspark before. > > Is there anyone know the solution? > Yes, this definitely sounds like a similar (or the same problem), but I didn't have time to check yet. Can anybody else observe the same problem? Cheers, Joschka |