forgot something. :-) Adi Oanca wrote: >>4) the way how the mouse cursor is currently moved will introduce a >>novelty in BeOS: a hanging cursor on load. > > Yes, I have talked about that with DW. We should collapse mouse > moved messages which come from input server. Unfortunately that is not > possible ATM because of BPortLink's architecture (at least, that was my > impression when I wanted to do that). > BMessages from input_server anyone? :-) > >>Instead, we should follow >>the path R5 has chosen, and use a direct handshake for updating the >>mouse cursor position only (note, the view transfer messages are still >>done over the standard message path, only the *visual* position update >>is not, since that's all that matters for perception). I don't understand... Are you talking about redirecting B_MOUSE_DOWN messages to the client BLooper? I remember sawing something like this in R5. (redirect_input_server() was called, I think) Thanks Adi.