Import Selectable Points from Excel or Data 1

[ewh]

Once you have the curve in the model, you can extract the definition points.

"Good to know you got shoes to wear when you find the floor." - [small]Robert Hunter[/small]

 

[Buckshott00]

Okay, how do I do that?

 

[ewh]

Insert -> Point Set -> Spline Points, Defining Points

"Good to know you got shoes to wear when you find the floor." - [small]Robert Hunter[/small]

 

[Buckshott00]

Perfect! Got it Thanks!!!

 

[cowski]

Insert -> Datum/Point -> Point Set, choose the spline points type and the defining points subtype. If you plan on deleting the spline so that you are left with only the points, uncheck the associative option under settings.

 

[moudy1]

You could use the journal C:\Program Files\UGS\NX 7.5\UGOPEN\SampleNXOpenApplications\.NET\File2Points\file2points.vb
You will need to open your file in notepad and replace the tab between the numbers with a comma.

 

[Buckshott00]

Thanks guys!!

 

[Buckshott00]

Sorry to bring back a thread, but I can't seem to create the initial spline anymore. I keep looking for points from file on the studio spline dialog or in the expressions dialog but cannot find it. Thank you

 

[cowski]

Don't use 'studio spline', use the plain old 'spline' command; it will have the 'through points' -> 'points from file' option.

 

[Buckshott00]

Thanks cowski, had to use the search as it wasn't on my menu

 

[JohnRBaker]

Note that are starting to be more 'aggressive' in terms of turning OFF menu items for functions which are either all but obsolete or no longer considered mainstream. Now there are several levels of this effort using different means depending on how serious we are in discouraging the use of these older functions.

The most draconian approach is to completely remove a function (with NO provision for reactivation) which is very rare but sometimes necessary. A recent example being the final removal of all Assembly Mating Condition dialogs in NX 7.5. As I said these were rare cases, but in my opinion, they should be less rare.

Then there is the removal of functions but with a provision to reactivate them if someone feels that that can't live without something. Personally we have way too many of these laying around, but that's generally not my call, so...

Then we have the situation, which the old general 'Spline' function where we have not removed the code but simply removed the item from the menu/toolbar, however we've provided you the ability to reactivate it using the Customize tools. Now we have no problems wiht people using Customize to reactivate these older, but technically not yet obsolete functions, just that we wanted to make sure that it was the user who was making an explicit decision to reactivate as we would prefer that the newer functions be used instead. Generally speaking, we are not all that concerned when it's legacy users who wish to go back and reactivate some function which they have used for years and feel more comfortable with. However, we are concerned when new users are being told that something used to work differently or that an older function is available and they really should be using it instead. There is no reason for this to ever be the case. New users have at their disposal ALL of the tools and functions needed to do their jobs and they should learn to use these existing tools and functionality as they were intended to be used.

Now there is one last level of access which we employ and that is the various Roles and whether full or partial menus are supported. This is based on a sort of 80-20 rule, where approximately 80% of the people will only be using perhaps 20% of the functions on a regular basis and so we use Roles, and their nuances, so that users are not presented with more options and menu items than they really need to do their normal everyday tasks, and this is of a particular nature for new users learning NX or perhaps even CAD for the first time so this is why we offer so-called 'Essential' Roles and we offer the option to limit menu items. However, over time we expect people, as they learn to use the system, to use more comprehensive Roles, with perhaps Full Menus, or to eventually create their own custom roles where they decide exactly which menu and toolbar itmes are always accessible and which will still need an occasional trip to the Customize tools or the expeditious use of the 'Command Finder'.

Anyway, I hope this clarifies why things are as they are and what our philosophy is behind what and how it is that we are managing the content of the menus and toolbars.

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

http://www.siemens.com/plm

UG/NX Museum:

http://www.plmworld.org/p/cm/ld/fid=209

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