>Simply put, it is not true. The deal is the impact, if done at the VFP source code level, in all probability, would not be significant at all. That said, there are loads of things folks would like that taken individually, would not be a big deal. However, where do you draw the line. In this case, there are ActiveX Controls that do this sort of thing.

No there are not. ActiveX controls only solves a little part of the problem. I can't build a whole UI on dozens of different activeX controls. I certainly don't have to remind you that there are NO activeX control that can act as VFP containers.

You saying that this is not true, simply does not say me anything. You can't prove this in any way. Your arguments that timer are not lightweight holds no water either. Recently someone tested how lightweight timer where, Conclusion they don't require a lot of resources. Besides, these times only fires at regular intervals when the mousecursor is over the cool object. When the mouse has left the object the timer is disabled. when a certain piece of code is run, these timers won't fire. How do they have any impact on your programs performance ?? The only drawback is that the timer is an object and therefore it requires memory. I can't see this being much of a problem though.

This whole issue can be solved by the very minor enhancement solution JimB came up with, Just with an extra parameter to an existing event, just like this is already implemented with the OLEdragover event. I'd like to have two extra events, but if this is not possible i'd go for Jims solution.

>As a general part of a UI, it is not at all standard. Rather, it is the toolbar du jour behavior we see today. In a year or so, it will be something else.

How can you say? this behaviour was introduced with Office 97 and still exists today. These features will stay here for a while.

>If you can roll it yourself, or if it is available in an ActiveX Control, it is not likely it would make it into the product.

So all the VFP 6 enhancements (regarding internet, etc) shouldn't have been added, it wouldn't make it because it wasn't available by activeX controls ? You're talking nonsens here. You're simply saying: "Stop any further developement, enhancements should be provided by ActiveX controls."

>In reality, it is much ado about nothing. If you use containers, it is not a hard feature to implement. Lisa Slater came damn close to doing this. If there is something missing, I can't imagine it would be that hard to fix.

The leaks can't be fixed without the help of timers. Period. I've (and others) done enough research to come to this conclusion. You might be an expert in certain fields, but the VFP UI seems not to be one of them.

Walter,