Hi all, My experience with OOP is that, unless the designers are very careful, it is harder to write systems with very fast real time response for every condition. But LAxx is a very fast real time response kind of application. Encapsulation and inheritance are great for making a complex task easier to code, but they generally increase latency. That is the tradeoff, hide the detail to make the design task easier and less bug prone, recuce interaction issues, control interfaces between object, but increase the depth of the call stack to recover the hidden details. Given that LAxx 4.x seems to be more CPU intensive, the design may have become more heirarchical than LAxx 3.x. However I would still expect to see the general structure streamlined for speed rather than encapsulation. Most people reading this are probable going "huh" about now so I suggest this should move OT from here. As a software developer, I admire what Emagic have been able to achieve. Good work guys. Ray