Hi -
Do any of you have succeeded in finding some command to be used in a journal (compiled image), which will tell the NX session, that it shall NOT
update objects , while code is executed...
I problem right now with a specific program I have developed (3150 lines of code), is that when I initialized the tool on a active drawing-Sheet, there are some delay on runtime, because NX is trying to update a lot of objects...In the cue-line it's shown as: "Updating Objects..."
My program is used to place some custom tabularNotes on the drawingSheets, and let the user selecet some pre-dfined text values from dialog (BlockStyler)....
Everything working so fine - except these unnessary updates from the NX session....
But Nothing needs to be updated ,just because we place some tabularNotes on a drawingSheet...
Maybe can the command "SetUpdateLock" from the Class "update" be used to solve the problem..?
But I'm just afraid of that when this is set to updatelock is set to False - in the end of program, it will force system to update all again...
Maybe it is not nesseary to set to False in end of program ?
[highlight #729FCF]theSession.UpdateManager.SetUpdateLock(True)
theSession.UpdateManager.SetUpdateLock(False)[/highlight]
regards lklo
Do any of you have succeeded in finding some command to be used in a journal (compiled image), which will tell the NX session, that it shall NOT
update objects , while code is executed...
I problem right now with a specific program I have developed (3150 lines of code), is that when I initialized the tool on a active drawing-Sheet, there are some delay on runtime, because NX is trying to update a lot of objects...In the cue-line it's shown as: "Updating Objects..."
My program is used to place some custom tabularNotes on the drawingSheets, and let the user selecet some pre-dfined text values from dialog (BlockStyler)....
Everything working so fine - except these unnessary updates from the NX session....
But Nothing needs to be updated ,just because we place some tabularNotes on a drawingSheet...
Maybe can the command "SetUpdateLock" from the Class "update" be used to solve the problem..?
But I'm just afraid of that when this is set to updatelock is set to False - in the end of program, it will force system to update all again...
Maybe it is not nesseary to set to False in end of program ?
[highlight #729FCF]theSession.UpdateManager.SetUpdateLock(True)
theSession.UpdateManager.SetUpdateLock(False)[/highlight]
regards lklo