Layer sorting journal or macro?

[IvanNX]

For simple moving of features on proper layers is it better to use self made macro or to use journal (and that it is convenient to be shared with colleagues latter)? As I do not know how to make proper journal for this task, where can I ask somebody to help me with that, if journal is correct answer?

 

[Xwheelguy]

Hi Ivan,

I might be nitpicking but are you wanting to move FEATURES or any GEOMETRY? Two different things, in my opinion, but probably worth noting prior to devoting time to any journal authoring.

Tim Flater
NX Designer
NX 9.0.3.4 Win7 Pro x64 SP1
Intel Xeon 2.53 GHz 6GB RAM
NVIDIA Quadro 4000 2GB

 

[cowski]

Xwheelguy is correct in that the geometry gets moved to layers, not the actual features. NX blurs the lines a bit by reporting the "layer" of each feature in the part navigator; what it is really reporting is the layer that the feature geometry is on.

Anyway, I'd use a journal for this task, but then I'm a bit biased...

If you search this site for "layer journal" or something along those lines, I'm sure you will get several hits. It might be a good starting point for your own code.

www.nxjournaling.com

 

[IvanNX]

Sorry for confusion, I really do not want my blends to be on different layer than my solids So you are right I want different geometry on correct layers.
I made macro for it and journal for it, and I see journal works little more like what I want. I had to make part with all possible geometry in it and to move them with selection filtering to correct layers. I just hope that nobody will make some peace of geometry that I forgot and then complain about my journal But if that happened, can I make new journal just for that geometry and copy paste code to existing journal (I think it is ok, if I do not copy everything but just part of code that make selection and move it...)?

 

[BubbaK]

A "journal" is just a program, usually written in the VB language. NX and the VB compiler don't care how you wrote the program text. You can type it, use journsl recording, or copy/paste text from elsewhere. It doesn't matter -- in the end it's all just text.

Your program should have a "branch" where it does something useful with types of objects that don't get special handling elsewhere. That way, your code will still work even if it encounters object types that you didn't think about.