I understand what you're saying, but one of the reasons the protocol is used as little as possible is security
(Plus! has been blamed to cause a whole range of connection problems before, even when it didn't used anything from the protocol and didn't interfeared with the protocol at all). And there are probably many more reasons why it is done as it is done now.
If things where so easy
(and to show it isn't that easy to make a always working, no interfearing, reliable sniffer and stuff look at the few sniffers around which don't always work), it would have been done that way...
I'm not disputing the fact that more things could be done when the protocol is used, but only noting that there are reasons why something isn't done (yet).
------------
quote:
Originally posted by Plan-1130
well I guess you're right when you say it's nothing safer, but what I would like to do is send parameters too, including objects.
Besides using global variables (which I'm also not very fond of), there are other tricks you can use to still send parameters to the timers by using the timer's id itself.
Smart programming quite often also reduces the need for parameters to be passed (can't always be reduced to nothing, but quite often it can be reduced a great deal).
Nevertheless, it would indeed be nice that there could be optional parameters being passed to the timer event. But again this is far from easy to implement as the timer scheme being used is almost strait the one from Windows itself. Making it that Plus! itself quite probably must use global variables itself to pull it off. In other words, there would be no advantage (memory wise) to it also.
/ 
