Forum unknown
· Programming
#GetMsg
5 messages in this thread
Hate to intrude since I'm not sure what you guys are talking about but
according to my M68000 manual the only form of moveq is LONG. There is no
moveq.w instruction.
Right you are. I was thinking of clr. What we were talking about was the
fact that I can get messages from my window's UserPort just fine as long as I
don't Reply(). If I do, poof. — Mike
Mike,
by Reply() I think you mean ReplyMsg(). The only thing I could think
could be causing a problem is that you are calling ReplyMsg() to soon. If you
are accessing any of the fields of the message after you reply the system will
crash. By calling ReplyMsg() your telling intuition that it can do anything
with the message it wants. If this doesn't help sorry. I don't really know what
your code is like but I have used the userport form a window with no problem.
Darrel
Mike,
by Reply() I think you mean ReplyMsg(). The only thing I could think
could be causing a problem is that you are calling ReplyMsg() to soon. If you
are accessing any of the fields of the message after you reply the system will
crash. By calling ReplyMsg() your telling intuition that it can do anything
with the message it wants. If this doesn't help sorry. I don't really know what
your code is like but I have used the userport form a window with no problem.
Darrel
Right you are. I was thinking of clr. What we were talking about was the
fact that I can get messages from my window's UserPort just fine as long as I
don't Reply(). If I do, poof. — Mike