dillon@CORY.BERKELEY.EDU.UUCP (04/02/87)
In my work with V1.21 of DME, I had to figure out how to be able to have multiple windows use the same IDCMP port (meaning the # of signals you have no longer limits the number of windows you can have open). Obviously I succeeded, since DME 1.21 has been released. But I noticed something with ModifyIDCMP() I was wondering if somebody at C-A (or anywhere) could enlighten me on it a bit: If you ModifyIDCMP() of a window down to, say, a single flag (NOT 0), is there a time window after the ModifyIDCMP() in which intuition will still post a message in a class which you NO LONGER have enabled? This seemed to happen to me, but I'm not sure. I did a ModifyIDCMP() down to a flag which I never use and never get on a window which I just openned and which previously had the IDCMP ACTIVEWINDOW flag set. Right after the ModifyIDCMP(), I check the message list on the IDCMP port and find no messages for that window which I just openned. However, it would seem that intuition posts the ACTIVEWINDOW message anyway, even though the IDCMP flags now do not have the ACTIVEWINDOW flag set (though they did when I openned the window). Whew: OpenWindow() IDCMP has ACTIVEWINDOW flag set ModifyIDCMP() IDCMP no longer has ACTIVEWINDOW flag set Check UserPort for msgs from window (none found) <ACTIVEWINDOW Message seems to come in> I say seems because it is possible that there is an error in my test program. If anyone at Commodore can tell me if this "message of class which used to be here but isn't now getting posted to the port AFTER the ModifyIDCMP()" is possible or not, I would appreciate it. BTW: You don't have to worry about this in DME 1.21, I use a foolproof approach... I think. In anycase, I've tested the thing with 70 open windows! (it took 20 seconds for intuition to update the layers whenever I closed a window !). BTW II: Nobody use DME V1.20... it's too buggy. So far, I haven't found any bugs in V1.21, which I posted yesterday. -Matt