Customization.ui

[bmozley]

Creo Community,



I just installed build M050, and normally I copy my customization ui
file (creo_parametric_admin_customization.ui) to :

C:\Program Files\PTC\Creo 2.0\Common Files\<build>\text



This is not working. Any ideas?



Brad

[cdspk]

I've found with an externally loaded file it doesn't recognise it first time, you have to Import it from the menu customisation window then it fixes, make sure you apply all customisation or it will only apply to the current interface.

I ended up making a little list of all the environments I work in as the customisation is seperate for each one, this is good once your up and running as each interface has different prioritites but is a bit time consuming initially, even part mode in the asm (RMB > Activate) has its own interaface,

[DonSenchuk]

Don't forget to add in the config line:

load_ui_customization_run_dir YES

Without this it won't read the file.

In Reply to Brad Mozley:

Creo Community,

I just installed build M050, and normally I copy my customization ui
file (creo_parametric_admin_customization.ui) to :

C:\Program Files\PTC\Creo 2.0\Common Files\<build>\text

This is not working. Any ideas?

Brad

[DonSenchuk]

This is not necessary. It also looks like a big time sink.

Try this:

1. Create the customization you'd like to use. You'll have to do this separately with each mode. (You said you have many different customization files already created. I'm not sure if you can simply load these sequentially or if you'll have to recreate a single customization.ui that incorporates each mode.)

2. Once each mode is customized the way you'd like, export the .ui file. Place it in your Start In directory. (Alternatively, if it's going to be used company-wide, rename it to creo_parametric_admin_customization.ui and put it in the load directory's \text folder.)

3. Add a config line: 'load_ui_customization_run_dir YES'

Now when you launch, it will pick up the new ui. No need to load up a bunch of customization.ui file every time you launch.

In Reply to Sean Kerslake:

I've found with an externally loaded file it doesn't recognise it first time, you have to Import it from the menu customisation window then it fixes, make sure you apply all customisation or it will only apply to the current interface.

I ended up making a little list of all the environments I work in as the customisation is seperate for each one, this is good once your up and running as each interface has different prioritites but is a bit time consuming initially, even part mode in the asm (RMB > Activate) has its own interaface,

[JayateerthaMala]

Hello all,
Does anyone have a 3D model of Intel NUC D33217GKE board that they can share?

Thanks,
Jay

[ocorten-2]

This the info I have put in our config.pro together with the config option.
It tells the whole story:

! Creo Configuration files are read from these locations (in this order):
!
! 1. %ptcwfroot%\.Settings
! Note: This is equivalent to %AppData%\Roaming\PTC\ProENGINEER\Wildfire\.wf\.Settings
! o Only .ui with the name: creo_parametric_customization.ui
! Note: UI changes will be stored here unless you set the option mentioned under #4
! These changes are supplementary on any admin file mentioned in #2
! o No other config files.
!
! 2. <creo load=" point=">\Common Files\<date code=">\text
! o Only .ui with the name: creo_parametric_admin_customization.ui
! Note: admin .ui files cannot be directly edited. Before editing, copy it to #1 or #4 as a normal .ui
! o config.pro, config.sup, menu_def.pro, protk.dat
!
! 3. %HOME% (c:\users\%username%)
! o Only config.pro, menu_def.pro, protk.dat (no .ui or .sup)
!
! 4. Start in directory
! o Only .ui with the name: creo_parametric_customization.ui AND when config load_ui_customization_run_dir is yes
! Note: System Info will only display filename: not entire path
! o Only config.pro, menu_def.pro, protk.dat (no .sup)
!
! Enable reading creo_parametric_customization.ui from startup dir
! See:
To: -
Date: 15-05-2013 01:00
Subject: [proecad] - Customization.ui



Creo Community,

I just installed build M050, and normally I copy my customization ui file (creo_parametric_admin_customization.ui)to :
C:\Program Files\PTC\Creo 2.0\Common Files\<build>\text

This is not working. Any ideas?

Brad








Site ...

[bfrandsen]

I did the same for both M030, M040 and now M050 without any problems at all.
I have not installed my Creo in C:\Program Files, but in C:\Programs to work arounds Windows 7 administrator rules for easy update from a network drive upon application launch.
/Bjarne

[dgschaefer]

I believe that it should read the creo_parametric_admin_customization.ui file from the text folder regardless of that config setting.

There is a problem with that setting, but it may not matter to you depending on how you work. This tells Creo not only to load the creo_parametric_customization.ui from the working directory, but to save it there as well. The problem comes when you change your working directory during the day.

You launch Creo with folder A set as the start in folder. The creo_parametric_customization.ui file found there loads at startup. You then change your working directory to folder B, your project folder, and begin your work. Along the way you add an icon to the quick access toolbar, prompting an automatic save of the creo_parametric_customization.ui file into folder B. Tomorrow, when you launch Creo, your new icon is not in the quick access toolbar because your creo_parametric_customization.ui file was not saved to the startup folder, folder A. Not to mention that you end up with creo_parametric_customization.ui files in all your project folders and if users share folders they overwrite each other's creo_parametric_customization.ui files.

--

[dgschaefer]

Is this always the case with newly copied files? I plan on creating a creo_parametric_admin_customization.ui file and copying it via my launch batch file into the text folder. Are you saying that it will have to be manually loaded each time? That's going to be a problem.

--

[DonSenchuk]

Since he had already mentioned he gave it the correct admin name, I didn't bother to point this out.

Since we WindchillPDMLink instead of working folders, this is something I had not encountered. Sounds like it's working similar to many other functions Pro/E has always done with regards to working folders. Not the most well thought out situation from PTC.

In Reply to Doug Schaefer:

I believe that it should read the creo_parametric_admin_customization.ui file from the text folder regardless of that config setting.

There is a problem with that setting, but it may not matter to you depending on how you work. This tells Creo not only to load the creo_parametric_customization.ui from the working directory, but to save it there as well. The problem comes when you change your working directory during the day.

You launch Creo with folder A set as the start in folder. The creo_parametric_customization.ui file found there loads at startup. You then change your working directory to folder B, your project folder, and begin your work. Along the way you add an icon to the quick access toolbar, prompting an automatic save of the creo_parametric_customization.ui file into folder B. Tomorrow, when you launch Creo, your new icon is not in the quick access toolbar because your creo_parametric_customization.ui file was not saved to the startup folder, folder A. Not to mention that you end up with creo_parametric_customization.ui files in all your project folders and if users share folders they overwrite each other's creo_parametric_customization.ui files.

--

[DonSenchuk]

No. It's my understanding that if you copy the admin .ui file into the correct folder - usually /text - AND you have the config.pro option set correctly, it will load it without issues. It's been around 6 months since I was testing this, but unless my memory is failing me it worked just fine once the config option was in place. No need to load it every time.

In Reply to Doug Schaefer:

Is this always the case with newly copied files? I plan on creating a creo_parametric_admin_customization.ui file and copying it via my launch batch file into the text folder. Are you saying that it will have to be manually loaded each time? That's going to be a problem.

--

[dgschaefer]

I thought the admin file would load from the text folder regardless of how that config option was set. Is that not the case?

--

[davehaigh]

Yes, if the admin file is down in the "common files\mXXX\text" folder and it has _admin_ in the name, it loads correctly.

If you have .ui files in multiple locations, they will combine. So you can have a company standard one in the loadpoint, and the user can have their own either in the cache directory or in the start-in directory.

I have a slide in my Creo Admin 102 presentation that I'll be giving at PTC Global in June, listing how I edit the company standard .ui file. I have a specific startup script just for editing this file.

My startup script does the following:

* Delete the loadpoint admin .ui file

* Delete the cache location .ui file

* Move the Start-in location .ui file to another loaction

* Copy the company standard .ui file to the start-in dir without admin in the name

This means you only have one .ui file that gets loaded. So any changes you make to it get stored back to that file.
Of course that's assuming you don't change working directories. Once you're done modifying it, you can manually copy it back to your central config location.

My startup script copies it down to the load point every time you start Creo.


David Haigh

[rreifsnyder]

We're getting set to go to Creo2 and we have an issue with custom icons in our customization.ui. Are these included in the .ui file? Or do we have to put the .png files somewhere?

TIA

Rob Reifsnyder
Mechanical Design Engineer/ Producibility Engineer / Components Engineer / Pro/E SME / Pro/E Librarian
[LM_Logo_Tag_RGB_NoR_r06]

[kimndave9]

Creating models when pictures are available but fully dimensioned
drawings are not:

If a PDF is available, convert it to DXF with software like Ghostscript
with pstoedit (has worked), Inkscape (should work), or Adobe Illustrator
(should work). Import the DXF into a drawing and delete any geometry you
don't like. It will be easier if the geometry is moved to the drawing
origin (lower left corner) or the drawing origin is moved (look under
grid properties) to a desired place on drawing. Move any geometry that
will be retained, but not exported, to other sheets. Export an IGES file
from the desired sheet. The IGES file can be imported as a feature into
a model and used to create geometry based on the curves in the feature.
If multiple views are available, create new coordinate systems to place
the different views appropriately.

This works well for circuit boards and test equipment. For circuit
boards the silkscreen is sometimes available, identifying all the
components for reference. For test equipment, it places cooling holes
and panel markings without having to create related, expensive geometry.

If a bitmap is available, edit it to be clipped exactly to the borders
of the item. Use this as a bitmap for a texture. Create a surface
exactly the size of the item and apply the texture as a decal. Pro/E
doesn't maintain the aspect ratio or size, so it is important that the
surface and the bitmap have matching aspect ratios and the surface be
the correct size. Also note that holes can be created in the bitmap
eliminating the image with it, but any border trimming will cause Pro/E
to resize the bitmap to match. Remember to use the configuration option
to store the bitmap within the model - save_texture_with_model yes.

Typical error for item locations with moderate size bitmaps are less
than 1%.

Trace over the bitmap to create features and dimension as desired. As
dimensions become available, e.g. interface locations, the dimensions of
the features can be altered as required.

Dave S.

[ocorten-2]

They are included in the .ui file.

You can import images as png files.

You can also use Copy Paste to copy custom created icons from earlier PTC releases.


Kind regards,

Olaf Corten




Olaf Corten
CAD/PLM Manager
Besi Netherlands B.V.
Ratio 6, Duiven
Phone: +31 26 3196215
Mobile: +31 644548554
www.besi.com






From: "Reifsnyder, Robert" <->
To: "-" <->
Date: 15-05-2013 17:50
Subject: [proecad] - RE: Customization.ui



We’re getting set to go to Creo2 and we have an issue with custom icons in our customization.ui. Are these included in the .ui file? Or do we have to put the .png files somewhere?

TIA

Rob Reifsnyder
Mechanical Design Engineer/ Producibility Engineer / Components Engineer / Pro/E SME / Pro/E Librarian

Mission Systems & Training (MST)
497 Electronics Parkway
Liverpool, NY 13088
EP5-Quad2, Cube 281
work: (315) 456-4307
cell: (585) 319-8185
-

ASME Senior Level Certified GDTP S-3014