

For example, the solid modeling kernel, Parasolid, is a 'module' which could be called several times during the execution of the single task.
Siemens step 7 cir register object software#
NX is actually a collection of software 'modules', performing different tasks and which can be reused by different applications.

No, I was NOT referring to 'modules' in the sense of 'products', but rather in how software is architected. To an Engineer, the glass is twice as big as it needs to be. That's just the nature of modern software/hardware architectural liminations. Sure, we'd like a universal 'Halt whatever you're doing and do mess anything up' button, but they just don't exist and probably never will. Of course, any operation which is writing information to the disk cannot be halted before the operation is complete and the written data verified that its valid and complete. Also, with the nature of virtual memory, the application isn't always in a state where if it were halted it could resolve what it had or had not yet written to memory.

If you do NOT see the 'Work in Progress' window, with an included 'Stop' button, then there is nothing that can be done to halt the current task in a safe and risk-free manner.ĭue to the nature of NX using many modules which are basically 'black boxes', like Parasolid, it it very difficult to halt the operation of some task when you don't have any direct control over what's happening behind the curtain. We already have a 'Stop' button in NX, and it will appear in the lower left corner of screen, inside the 'Work In Progress' window, WHENEVER the task being executed is one which CAN be halted without losing anything or where there is no risk of corrupting the model or the session.
