MPSTART 2,"1" WHILE 1 LINPUT"";T$ IF LEN(T$)>0 THEN MPSEND T$ MPSET 0,1 WHILE !MPGET(1,0) WAIT WEND WAIT WENDGUEST SYSTEM
MPSTART 2,"1" WHILE 1 WHILE !MPGET(0,0) WAIT WEND MPRECV OUT ,T$ PRINT T$ MPSET 0,0 WAIT WENDJust in case the code is wrong, the purpose of the program was to take input from the host system, send it over to the guest system and wait for its confirmation, then start over again. The output of the program was constantly printing out T$ to the guest system regardless, while when I had stopped the program to check the state of the registers using MPGET, I found MPGET(0,0) was 0. I'm not quite asking for a solution to my problem, I just want to know if there are any special things about MPGET and MPSET I should know. Do they take up more than one frame to read and send, while still maintaining program execution? Could it be the MPSEND which creates some kind of delay? MPGET requires for its first parameter a value denoted as the 'Terminal to read from' or something like that. Why would MPGET need to know from which terminal to "read" from if the registers are universal among all connected systems? It must mean that the registers are not universal, and that each register pertains to its own system, right?
Check the usage of the first OUT parameter of MPRECV. I believe a negative value indicates that no new message was received, meaning the contents of T$ is undefined.So the halt and continue system I'm trying to use is not relevant because I can check the first OUT parameter for a negative value? That's actually useful. I read in the manual that using MPSEND over some (undefined) rate will result in a Stack Overflow error, which seems to be untrue for repeatedly changing the values of the registers. The registers seem to be a valuable tool for multiplayer communication, and I just don't understand why my setup didn't work. Edit: Could it be that MPSET on the guest system cannot change the value of a register on the host system because the registers are not universal among all connected systems?
It's too bad there's no way to check how full the MPSEND buffer is. If you send more than 4 strings without them being received, data will be lost.
MPSTART 2,"1" WHILE 1 MPSEND"A"*128INC N?N WAIT 2 WENDIt seems to send it without error continuously, but it loses its data? Edit: I tested this, and it seems to replay the hundreds of MPSENDs "sent" to it.
It seems that MPSEND stores the data it "sends" onto the system-that-sends; no information is transmitted when MPSEND is called, only when MPRECV is called. (I wonder what the Communication buffer overflow error really is ... )I don't think this is quite accurate. I think when MPSEND is executed, it stores the message in an outbound queue stored locally on the console. Periodically (maybe approx. once every 2 frames, IIRC), everything in the outbound queue is transmitted, regardless of MPRECVs happening or not happening on other consoles. An overflow error occurs if this outbound queue overflows. When messages get received, they get added to a 16-deep inbound queue. If a message is received when the queue is full, no error occurs, the last element of the queue gets overwritten. I hope I'm remembering all that right. EDIT: here it is: http://smilebasicsource.com/forum?ftid=171 Odd: it belongs in Bug Reports, I'm pretty sure I didn't put it in Programming Questions. Someone misfiled it, apparently. - Hey 12, you're an admin, can you put it back where it belongs? And, now that I see this, it has me a little concerned - is there an easy way to find out if other posts of mine have been misfiled?
I investigated this a while back, and I thought I reported my findings on SBS, but I can't find it. Maybe it was moved or deleted, or maybe I'm misremembering.I might have accidentally moved it while I was cleaning up the bug reports forum a while ago. It's back now.It seems that MPSEND stores the data it "sends" onto the system-that-sends; no information is transmitted when MPSEND is called, only when MPRECV is called. (I wonder what the Communication buffer overflow error really is ... )I don't think this is quite accurate. I think when MPSEND is executed, it stores the message in an outbound queue stored locally on the console. Periodically (maybe approx. once every 2 frames, IIRC), everything in the outbound queue is transmitted, regardless of MPRECVs happening or not happening on other consoles. An overflow error occurs if this outbound queue overflows. When messages get received, they get added to a 16-deep inbound queue. If a message is received when the queue is full, no error occurs, the last element of the queue gets overwritten. I hope I'm remembering all that right. EDIT: here it is: http://smilebasicsource.com/forum?ftid=171 Odd: it belongs in Bug Reports, I'm pretty sure I didn't put it in Programming Questions. Someone misfiled it, apparently. - Hey 12, you're an admin, can you put it back where it belongs? And, now that I see this, it has me a little concerned - is there an easy way to find out if other posts of mine have been misfiled?
