# Vision: Best way to get the Window's rootContainer object from a component **URL:** \ **Category:** Ignition\ **Created:** [July 5, 2019, 8:10am UTC](https://forum.inductiveautomation.com/t/vision-best-way-to-get-the-windows-rootcontainer-object-from-a-component/26309 "2019-07-05T08:10:49Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [July 6, 2019, 1:45pm UTC](https://forum.inductiveautomation.com/t/vision-best-way-to-get-the-windows-rootcontainer-object-from-a-component/26309/8 "2019-07-06T13:45:57Z")
You are encountering Ignition's spotty application of its PyComponentWrapper, which is responsible for making custom properties act like regular properties. For more details, see this thread: > [@Transaction groups triggered expression item updating when trigger is false](http://forum.inductiveautomation.com/t/transaction-groups-triggered-expression-item-updating-when-trigger-is-false/17196/14): > > Ok, so I’ve been down the rabbit hole and found Ignition’s (undocumented) PyComponentWrapper. I haven’t deciphered it enough to be sure, but it seems to be invoked only for particular situations, based on the string constants in the class file (like “getComponent” and “getComponents”). To play with this, I constructed a conversion adapter like so: public class PyComponentAdapter implements PyObjectAdapter { public PyComponentAdapter() {} @Override public boolean canAdapt(Object jObj) { … TL/DR: Install a current version of my [Simulation Aids](https://inductiveautomation.com/moduleshowcase/module/automation-professionals-llc-simulation-aids) module. --- _[View the full topic](https://forum.inductiveautomation.com/t/vision-best-way-to-get-the-windows-rootcontainer-object-from-a-component/26309)._