Geomagic Points Beyond Blog

When your scripting solutions become more complex...more powerful...you will most likely need to share values between functions and scripts. You might even need to share information with programs outside of the GPSE.

The Geomagic Python Scripting Environment (GPSE) is just that...an environment...it can be thought of as a door or window to the current session or process of a running Geomagic industrial application...a programming interface to your data and our technology. Each of our v2012 industrial applications: Geomagic Studio/Wrap/Qualify/Probe v2012 includes this programming interface.

Note: You can now find the GPSE Help through the standard Geomagic Help by pressing the Help Button in your open application, looking up "About Scripting" in the Search Tab, and opening the Scripting Documentation link to the html help system.

So, where am I going with all this...well, I am simply framing the nugget for this week. The enviroment, the GPSE, is alive as long as the application is running...and it is in this enviroment that you can create and share objects: variables, classes, and functions (models, features, numbers, strings, code, etc.) in and between not only your functions in your script, but also with other scripts and even programs outside of the GPSE. How do you share data between scripts? Enjoy this weeks GPSE snack...

The latest in a series of posts by Geomagic COO, Tom Kurke, who is intrigued by the current state of Intellectual property laws, or more precisely the lack of them, and the effect it is having on protecting your designs in 3D.

It doesn’t matter whether you believe that the current boundaries of intellectual property protection do not go far enough to protect the rights of content creators or if you believe that copyrights, patents and other forms of intellectual property protection have been stretched well beyond their intended scope – the conclusion still remains – “Houston, we have a problem.”