Welcome, Guest. Please login or register.

Author Topic: WaitSelect() with Reaction  (Read 2848 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline PiR

  • Full Member
  • ***
  • Join Date: Apr 2003
  • Posts: 148
    • Show all replies
Re: WaitSelect() with Reaction
« on: September 23, 2003, 02:47:49 PM »
Hi

It was not so easy, but I've found it for you!
According to this thread, the Rogue's answer, socket notification is also done with task signals, so I think that you should give a long vacation to WaitSelect(), check the signal number of the socket, create a mask with all signals you need, and give a chance to Wait()...

The other solution could be two tasks - one for socket, the other for GUI. But you'll have to make yourself a possibility to wake up the task waiting on socket somehow, at least to have the ability to close it, while the is no activity on socket.

But to be honest - I have NULL Reaction experience.

Good luck
 

Offline PiR

  • Full Member
  • ***
  • Join Date: Apr 2003
  • Posts: 148
    • Show all replies
Re: WaitSelect() with Reaction
« Reply #1 on: September 26, 2003, 11:50:02 AM »
Hi again.

I did downoad AmiTCP_SDK just to look at it.
Ok, there is no way to find this signal out of the socket.

According to this thread, what Karlos is saying is that Reaction does some stuff in input.device task, which may mean even not signalling your task. Check it with some gadgets that HAVE TO be propagated to your task, like CloseWindow.

If this is case, then I think you'll have to make your own additional signalling.

Good luck