Thanks go out to Murrawhip for pointing out the massive CPU usage of window transparencies. Because of that, Prism will not use window transparencies. However, I was able to convert my positioning code to work for both external windows and screen objects. The attached demo shows the same basic code running on screen objects with transparencies. I could easily add an html window to the interface with a set anchor point also. This will, hopefully, blur the distinction between screen objects and windows in Prism. I may even be able to combine the two to make windows appear to have transparent borders. Who knows? Anyway, the demo uses probably less than half of the CPU as the original and has much smoother motion.

2011-09/NefariousDevelopment-0005/child_windows2.zip