Tools - Expressions
Tools - Expressions
(OP)
NX 7.5.1.5
One for John Baker.
John, up through NX7 we've been able to use the 'old' expression dialog (pre-NX3) by the use of a MEN file in the Startup folder (instructions were provided through GTAC).
Can you tell me whether this dialog is now finally retired in NX 7.5 ?
One for John Baker.
John, up through NX7 we've been able to use the 'old' expression dialog (pre-NX3) by the use of a MEN file in the Startup folder (instructions were provided through GTAC).
Can you tell me whether this dialog is now finally retired in NX 7.5 ?





RE: Tools - Expressions
BTW, if I discover that this is still possible with NX 7.5 I will personally see to it that it's removed for NX 8.0 once and for all.
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.
RE: Tools - Expressions
It's OK, we still love you.
thread561-280195: Problems with GTAC Support
RE: Tools - Expressions
If you provided a dialog that offered the same level of usability as the original, I wouldn't still be using it
The new one has a great choice of filters, but where's the filter allowing me search both sides of the = sign simultaneously ?
To be honest, the company I work for, whether they're new users (NX Seies), or old users (per-V10), once they've been shown the 'old' dialog, they never use the new one again.
Here's hoping it's still available, at least through NX7.5.
Failing that, I guess we'll have to write our own
RE: Tools - Expressions
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.
RE: Tools - Expressions
RE: Tools - Expressions
However, as for being able to open legacy part files (the file I keep for that demo, when it comes up, was last saved some 17+ years ago in UG V9.1), that's a totally different issue and has very little, if anything, to do with the 'look & feel' of the current User Interface or for that matter the performance of the system.
P.S. To keep myself honest I just tested opening that 17+ year old file in NX 7.5.2.4 and it worked just fine (next week I'll be testing an early phase of NX 8.0 and this'll be one of the first tests which I'll be doing ;-)
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.
RE: Tools - Expressions
I use Move Object and the new Hole dialog, never looked back, excellent improvements on the old stuff.
Don't get me wrong, I get the new expression dialog, it does make the old one look "OLD". Expression units though, don't need them. Just cause issues, especially when you get into interpart expressions.
As to a regression ... I had many conversations with GTAC (and Development) back in the NX3 days about this. A result of which was the inclusion of the 'Sort Ordering' and finally the ability to access the old dialog.
I guess my one outstanding complaint is the inability to filter on both sides of the = sign. Consider the attached image, is this possible with the current dialog ? Assuming it isn't, is it worth me calling it in as a regression ?
RE: Tools - Expressions
RE: Tools - Expressions
Now that being said, I did have a conversation yesterday with the team responsible for the Expression system and the relevant dialogs, and there is some recognition that perhaps it's time to make a few changes/additions, if for no other reason than to accomodate some significant enhancements being made in terms of some new types of Expressions that users will be able to create and use in other applications (which BTW will NOT be available to you if you're still using the legacy dialog).
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.
RE: Tools - Expressions
RE: Tools - Expressions
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.
RE: Tools - Expressions
RE: Tools - Expressions
RE: Tools - Expressions
ToolDia = Length
ExitAngle = Angle
Using the pre-NX3 Expression dialog, the following works :
ExitAngle=if(ToolDia>=14&&ToolDia<=16)60 else 0
With the current Expression dialog that would throw a "Dimension mismatch" error and I have to format it as per :
ExitAngle=if(ToolDia>=MM(14)&&ToolDia<=MM(16))60 else 0
So annoying !
RE: Tools - Expressions
check1=if(ToolDia>=14&&ToolDia<=16)60 else 0
And the second, with dimensionality 'Angle':
ExitAngle=check1
Granted, it's an extra Expression, but you don't need to mess with units when you're only performing a logic operation.
BTW, I may have some news in a few weeks on the issue for which you originally started this thread.
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.
RE: Tools - Expressions
This works :
ExitAngle=if(ToolDia=14||ToolDia=16)60 else 0
RE: Tools - Expressions
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.
RE: Tools - Expressions
tia
RE: Tools - Expressions
Anyhow, I'm looking forward to your forthcoming news.
RE: Tools - Expressions
If the user wants to apply restriction on the variable so be it.
The number if times I have set up a variable that I want to use in both linear and angular expressions only to be stopped with a dimension type conflict is painful. I have to go back and take the variable out of the linear equation reset it to constant, reinsert it in the linear equation then add it to the angular equation.
Defaults should always be the most flexible option.
RE: Tools - Expressions