SadAboutENEX11 wrote:...icon sizes smaller than "normal". That alone would help me tremendously...
When in customize, Right click on the icon and size options are pretty comprehensive, is that what you meant?
↧
Re: NX Classic Toolbar User Interface Will Retire from Windows in NX 11
↧
Re: NX Classic Toolbar User Interface Will Retire from Windows in NX 11
Here are my options (and current settings). As you can see, the results are not small. It's like it setup to automatically go to the biggest size possible based on how big the NX window is, regardless of the settings.
↧
↧
Re: NX Classic Toolbar User Interface Will Retire from Windows in NX 11
It would be a timesaver if you could change the icon size by groups or tabs. Now you have to change every icon individually. It would be logical if you could at least have a group setting for the icon size.
Another thing that I would like to see if you can copy or reference a radial popup from one application to another. Not everything is useful. A radial popup with your favorite synchronous modeling commands would be useful in modeling, sheetmetal and manufacturing for instance. Now you have to make the same popup three times.
↧
Re: NX Classic Toolbar User Interface Will Retire from Windows in NX 11
Hi
A little trick I learned this week is when you have the Customize dialog open, right click on a group name, and from the popup menu choose "Content and Style > Flow Layout". This changes a group from this:
To this:
Regards, Ben
↧
Re: Part not loaded report
Ug_inspect -cmod doesn't return anything related to linked parts.
Perhaps you're looking for something else, however, from my test the WAVE linked parts were listed.
The following is returned using the -cmod switch with toycar_assy that has both linked geometry from toycar_body (which is also a component of toycar_assy) and Test (not a component of toycar_assy):
Number of external references out of this directory: 594 The external references are to the following data managers / directories / files Data Mgr Part Dir File Name -------- -------- --------- RM Record Mgr toycar_assy.prt (found in C:\Program Files\Siemens\NX 11.0\UGOPEN\SampleNXOpenApplications\.NET\AssemblyViewer)CM CMOD toycar_body.prt (found in C:\Program Files\Siemens\NX 11.0\UGOPEN\SampleNXOpenApplications\.NET\AssemblyViewer) RM Record Mgr toycar_body.prt (found in C:\Program Files\Siemens\NX 11.0\UGOPEN\SampleNXOpenApplications\.NET\AssemblyViewer)CM CMOD Test.prt (found in D:\GTAC\Community\Model Letter T) RM Record Mgr Test.prt (found in D:\GTAC\Community\Model Letter T)
Regards, Ben
↧
↧
Re: NX Classic Toolbar User Interface Will Retire from Windows in NX 11
It would also be helpful if I could get more details from you and others what you dislike about the ribbon UI other than "more clicks".
I can't speak for anyone else but that's my issue: it's pretty but counterproductive requiring more user input for the same execution. If you've release a regression that slows down 10's of thousands of users isn't that enough of a problem to tackle?
Our customization tools are very powerful compared to Microsoft and our border bars are unique to the NX ribbon. We feel that border bars are an easy way to add more commands to the ribbon UI therefore resulting in fewer clicks.
I'm finding that's true and the functionality is mostly there to use the border bars for a 'legacy-like' interface. The user then hides the ribbon bar which it is not used.
If the most experienced users are doing this what does that tell you about the success of this new ribbon UI?
Let me turn this around: please instruct me on the thinking behind the ribbon UI and what productivity studies were done before implementing? All we have heard so far is that you rolled it out to a few beta testers and they seemed to like it.
If veteran users can customize the UI to get what we need for productivity (which seems to be true) I would say there is no problem there but teaching new users the ribbon interface likely means they will never know how much more streamlined the UI can be which I think you would agree is not a good thing.
Speed and stability should be the dev team's top priorities.
↧
Re: NX Classic Toolbar User Interface Will Retire from Windows in NX 11
Mine doesn't look like that. It looks like this.
↧
Re: NX Classic Toolbar User Interface Will Retire from Windows in NX 11
All - one of the reasons I asked for mtx files is because there are various ways to achieve a toolbar layout, Flow Layout being one of them. After creating a new Tab, the other choices are:
1. Find the toolbars you'd like to use in the Customize dialog, Commands page, Classic Toolbars (As Groups) and drag them onto the tab.
2. Find the commands you'd like to use on the Commands page and drag them onto the tab.
3. Edit an existing gallery or create a new one. Set the On-Ribbon columns to the desired number (MB3 on the gallery).
4. Change groups to Flow Layout
You can also try turning on the Slim Ribbon Style in the User Interface Preferences dialog, Layout page.
I have heard it's difficult or not possible to attach files, so feel free to email them to me Laurie.McAllister@Siemens.com
Thanks, LaurieM
Thanks, LaurieM
↧
Re: NX Classic Toolbar User Interface Will Retire from Windows in NX 11
Thanks, LaurieM
↧
↧
Re: NX Classic Toolbar User Interface Will Retire from Windows in NX 11
Make sure you're in Customize mode as Laurie said, then RIGHT click, not LEFT click, on that small black arrow at the end of the Standard Group. Then you will see the options Ben was showing.
↧
Re: NX Classic Toolbar User Interface Will Retire from Windows in NX 11
Thanks, LaurieM
↧
Re: ERROR OPENING PRT (DRAFT) FILE
thanks for the info
↧
Re: NX Classic Toolbar User Interface Will Retire from Windows in NX 11
Good point about the flow layout. It turns out I enabled this long time ago. I didn't bother yet to go through customizing for NX12. I wonder how long it would have taken to me to rediscover the flow layout.
↧
↧
part not a valid version
So here's a fun situation; I'm cleaning up some older files. I set my load options as desired and when I open a particular assembly, one of the components gives me the message:
So I try to use "replace component" in an attempt to use this part file that was found. I then get this message:
So is it not a valid version or is it the same? It can't be both, right?
↧
Re: part not a valid version
Are you sure that the component you're using for the Replace Component command from the same folder that NX is finding the 'not a valid version" component?
Turn on "Allow Replacement" in the Load Behavior section of the Assembly Load Options.
Regards, Ben
↧
Re: part not a valid version
cowski1 wrote:
So is it not a valid version or is it the same? It can't be both, right?
I wouldn't rule anything out...
↧
Re: part not a valid version
That reminds me of a syslog entry we used to see from time to time: "Error catcher caught something"... but didn't explain further.
↧
↧
Re: part not a valid version
In your load options try turning on allow replacement in your assembly load options.. It seems we had this issue years ago, when updating our parts that were ran through the CMM process. Can't remember the details why this worked, I will try to find the details on our issue.
EDIT
If I remember correctly when NX opens a part from teamcenter it looks for a version number, since we were migrating and remigrating I-Deas parts to NX parts this would change the version of the NX part, Since the version number changed we would get this error. We turend this Allow replacement load option on and it solved the problem.
If we remigrated a part the version of the part would change.
↧
Re: part not a valid version
Turning on "allow replacement" let me open the assembly with the component version that I found but I get a message:
"Structure change to parent part caused component deletion during load"
Which I think means that NX had to delete the old version and add the new one? I'll need to reassociate a bunch of dimensions, but it's better than nothing.
Opening the part and looking at the part history reveals that it is a dumb body that was converted over from a step file. Based on this information and the folder it is currently in, I'd guess that we lost the original, parameterized file and we recovered this one from one of the toolmakers.
Thanks for posting that "error" message, it was the highlight of a very boring afternoon.
↧
Re: Hole inside Assembly
Check the following and if you need any clarifications, please let me know.
↧