×
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

NX Journal vs Macro - Why journals are much slower to run?

NX Journal vs Macro - Why journals are much slower to run?

NX Journal vs Macro - Why journals are much slower to run?

(OP)
In NX 10, I created a macro to change the transparency of a part to 60%, and I assigned the macro to a button. I did the exact same task using a journal.

When I click on the macro button, it immediately changes the transparency of the part. However, when I click on the journal button, it takes around 2 second to run the task. They both successfully changes the transparency of the part. But, I am wondering why journal is much slower than macro?

I tried to improve the speed of the journal by compiling it to a dll, but it shows exactly same slowness.

I appreciate any comment in this regard.

RE: NX Journal vs Macro - Why journals are much slower to run?

I have noticed the same, and curious if somebody can explain this.


Regards,
Tomas

RE: NX Journal vs Macro - Why journals are much slower to run?

If you run the journal again, is the time less?

Mark Rief
NX CAM Customer Success
Siemens PLM Software

RE: NX Journal vs Macro - Why journals are much slower to run?

If you run your code as a "journal" file, the code needs to be compiled and loaded into memory before it is run. The compiling and loading step can take a moment or two. Since you have compiled your code to a dll file, it no longer needs to be compiled, but it still needs to be loaded into memory. To speed your code even more, you can change the "unload option" to "at termination", recompile your code and place the resulting dll file into the NX "startup" folder. Doing so will load your code into memory when NX loads and it will stay in memory until the NX session is terminated.

www.nxjournaling.com

RE: NX Journal vs Macro - Why journals are much slower to run?

Kowski,
Isn't there a way to load the .dlls at ug startup but leave them into the "Application" folder ?
A specific variable maybe ?

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!


Resources