Switch from model to drafting

[cubalibre000]

Hi,
my steps that I use to go from the model to his drafting, it seem absurd, I hope I am wrong.
As suggested by Siemens, I keep separate the model to his drafting.
To make this switch, I make these steps:
1) From the model I select the Windows menu and select his specification
2) Once I do this I'm in the modeling specification
3) At this point I click on Start menu 'NX drafting' or I type Ctrl + Shift + D

To switch from drawing to model performs the same procedure in reverse.

There seems absurd?
Do not talk about it if I'm changing a part in the assembly environment and I have to go to his specification.

Do you make the same ?

Regards,

 

[JohnRBaker]

That's the way it has worked since UG V10.0, some 16+ years ago. This is what we call the 'Master Model' approach. Note that it generally works better if you open the Drawing first, but in either case you will still have to go to the 'NX Start' menu and change modules to go from Drafting to Modeling.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[tomstickland]

I agree that it's a bit silly.

I had a thread on here a while back asking why it can't remember which application you're running in each window and then automatically switch when you change windows.

I was told that it was a lot more complicated than I thought, but that's what software developers always say when they don't want to do something (I do a fair bit of software too).

 

[JohnRBaker]

The problem is that this concept of multiple files each in their own 'window' is merely a presentation scheme and has nothing to do with what's actually happening inside the real-time database that's loaded in memory. There is only ONE database with multiple files loaded together. Now when you think of an assembly where the details parts are loaded along with the assembly structure, it's logical and no one questions it that much, but this is still the same scheme that is used even if multiple files are opened which have no relationship to each other at all and yet they are still all loaded into the same memory space. And because of that there is no practical way to track which module would be the logical one to open when changing from one 'window' to another. Now it is true that we remember what module was in effect when you SAVE your part file and if that is the ONLY file opened (no other files currently open) then we will restore the module when last saved, but that's the only condition where this is practical to do.

John R. Baker, P.E.
Product 'Evangelist'
Product Design Solutions
Siemens PLM Software Inc.
Industry Sector
Cypress, CA

http://www.siemens.com/plm

http://www.plmworld.org/museum/

To an Engineer, the glass is twice as big as it needs to be.

 

[JonSelby]

I've seen this pop up on here before although its never particularly bothered me.

Seeing as this may be a common concern (independently my colleagues have griped about this too) I'm wondering whether it would make sense to have the facility to set a 'file associativity option' (with the default being to do nothing).
For example you could set the option that specifictions always go into drafting (and maybe you could hold down shift or alt if you don't want it to).
I guess this is similar to windows where you plug in your camera and it asks you what you want to do ... then you can select to 'always do this'!

Just a thought from a user who doesn't program software ...

 

[hudson888]

Theoretically you might be able to run an attribute with a customisation if it really is necessary to you. In terms of the program and the flexibility that NOT having distinct model versus drafting type files allows you to do a quite a few things in NX that other software won't. Users coming from other systems may complain initially, but then being able to think outside of narrower constraints has its benefits for more experienced users that we probably wouldn't like to sacrifice.

Best Regards

Hudson

www.jamb.com.au

Nil Desperandum illegitimi non carborundum

 

[tomstickland]

And because of that there is no practical way to track which module would be the logical one to open when changing from one 'window' to another. Now it is true that we remember what module was in effect when you SAVE your part file and if that is the ONLY file opened (no other files currently open) then we will restore the module when last saved, but that's the only condition where this is practical to do.

Each window that's available in the list of windows should be able to remember which application it last used during the session.
That's got nothing to do with databases and I still don't understand what is so difficult about implementing this.

There is clearly an internal list of all the windows that can be viewed, so add an application field to the data.
When a window is selected look in that list to see which application is required and put the system into that mode.
Have a preference to turn this off.