[HELP]Mapkey to record edit of infamous linear_tol_0_0 and similar

[BG_9869104]

Creo version:7.0.3.0

Issue: not able to record a mapkey to edit linear_tol_0_0 or other similar parameters in existing parts/asm/drws.

Scope: updating legacy parts, updating parts designer used a save copy as to create new similar part from old. Changing the parameters anytime for different customers or same customer wanting the defaults changed. MBD and/or DRW. Mapkey solution able to be distributed to multiple users and function.

Current manual methods of edit:

Spoiler

Current limited method of manual edit: with tol_display on some of the items are in the lower right corner of the graphics window. Have to set selection filter to annotations. Then double click on item. Enter new value to. Enter. Repeat for the few listed. 

Current method to update all manual method:

Add a note and input the parameters:

&linear_tol_0_

&linear_tol_0_0

...

&linear_tol_0_000000

&angular_tol_0_

&angular_tol_0_0

...

&angular_tol_0_000000

With the note made now double click on each to bring up the edit value dialog. Input new value, enter, repeat for all 14. Then select the note and delete it.

None of the manual methods seem to give usable mapkey recording methods. Looking for alternate method of accessing these seemingly special parameters so I can Mapkey the edits. Below are the trail file outputs with cmdmgr_trail_output toggled.

Code in Spoiler:

Spoiler

Code:

cmdmgr_trail_output yes

~ LButtonArm `main_dlg_cur` `proe_win` 9 1432 960 0 1 1566 1035 2560 1440 156402029
~ Move `main_dlg_cur` `proe_win` 9 1432 960 0 1 1566 1035 2560 1440 156402032
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 1432 960 0 0 1566 1035 2560 1440 156402113
@ sel view 0
 1.889157 0.000000 0.000000 0.000000 1.889157 0.000000
 0.000000 0.000000 1.889157 477.371130 142.557044 -1675.418056 0.327680 0.000000 0
@ stack attr 8
@ stack attr -1 0  1
@ sel2d 0 TEXT_TAG 
3 4
@ stack idx 0
@SEL_REC 0 [] 14 4 -1 (0.0000000000 0.0000000000) (2692.9198957041 -522.0386131243 0.0000000000)
!Text
~ LButtonArm `main_dlg_cur` `proe_win` 9 1432 960 0 129 1566 1035 2560 1440 156402199
!Command ProCmdEditValueDim was pushed from the software.
!%CPEnter value for linear_tol_0_0 [0.3]
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 1432 960 0 256 1566 1035 2560 1440 156402349
!%TR
.2

cmdmgr_trail_output no

~ LButtonArm `main_dlg_cur` `proe_win` 9 869 692 0 1 1566 1035 2560 1440 156532967
~ Move `main_dlg_cur` `proe_win` 9 869 692 0 1 1566 1035 2560 1440 156532970
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 869 692 0 0 1566 1035 2560 1440 156533064
@ sel view 0
 1.889157 0.000000 0.000000 0.000000 1.889157 0.000000
 0.000000 0.000000 1.889157 477.371130 142.557044 -1675.418056 0.327680 0.000000 0
@ stack attr 8
@ stack attr -1 0  1
~ LButtonArm `main_dlg_cur` `proe_win` 9 1434 959 0 1 1566 1035 2560 1440 156534770
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 1434 959 0 0 1566 1035 2560 1440 156534824
@ sel view 0
 1.889157 0.000000 0.000000 0.000000 1.889157 0.000000
 0.000000 0.000000 1.889157 477.371130 142.557044 -1675.418056 0.327680 0.000000 0
@ stack attr 8
@ stack attr -1 0  1
@ sel2d 0 TEXT_TAG 
3 4
@ stack idx 0
@SEL_REC 0 [] 14 4 -1 (0.0000000000 0.0000000000) (2697.8955877896 -519.5507670815 0.0000000000)
!Text
~ LButtonArm `main_dlg_cur` `proe_win` 9 1434 959 0 129 1566 1035 2560 1440 156534906
!Command ProCmdEditValueDim was pushed from the software.
!%CPEnter value for linear_tol_0_0 [0.2]
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 1434 959 0 256 1566 1035 2560 1440 156535059
!%TR
.1

These parameters are saved in model files but not in a useful place like the .dtl detail area that would be easy to import an update.

Workaround? naw:

Spoiler

The workaround I do not want to do is abandoned all these built in parameters that are supposed to do the job and make similarly named params in every model to use. Then I would have to find and update every note that has the system parameter in it. Update all Plus the defaults in Creo that are also save in the model and can be displayed on screen will be wrong.

Can make params of the same name in the parts, what! Wow.

Spoiler

Another bad thing is users can add parameters of the same name in the model. Those user added clones work within parameters and relations but not outside of that. When using in a note (&linear...) the system parameter is shown not the user created one.

Additional note: How to display the set tol for dimension with zero decimal places

Spoiler

Additional note there is an old locked thread asking how to display the linear tol for no decimal places shown on a dimension. There is a way to set that in the config which is known with alternate input method in config.pro. 

Regular config.pro starts at one decimal place

linear_tol_0.0 0.25

Optional input method of the same setting

linear_tol 1 0.25 2

Optional input for zero decimal places

linear_tol 0 0.5 1

The way to display that in a note/title block or other location is "&linear_tol_0_"

[MartinHanak]

---

@BG_9869104 wrote:

Creo version:7.0.3.0

Issue: not able to record a mapkey to edit linear_tol_0_0 or other similar parameters in existing parts/asm/drws.

Scope: updating legacy parts, updating parts designer used a save copy as to create new similar part from old. Changing the parameters anytime for different customers or same customer wanting the defaults changed. MBD and/or DRW

Current manual methods of edit:

Spoiler

Current limited method of manual edit: with tol_display on some of the items are in the lower right corner of the graphics window. Have to set selection filter to annotations. Then double click on item. Enter new value to. Enter. Repeat for the few listed. 

Current method to update all manual method:

Add a note and input the parameters:

&linear_tol_0_

&linear_tol_0_0

...

&linear_tol_0_000000

&angular_tol_0_

&angular_tol_0_0

...

&angular_tol_0_000000

With the note made now double click on each to bring up the edit value dialog. Input new value, enter, repeat for all 14. Then select the note and delete it.

None of the manual methods seem to give usable mapkey recording methods. Looking for alternate method of accessing these seemingly special parameters so I can Mapkey the edits. Below are the trail file outputs with cmdmgr_trail_output toggled.

Code in Spoiler:

Spoiler

Code:

cmdmgr_trail_output yes

~ LButtonArm `main_dlg_cur` `proe_win` 9 1432 960 0 1 1566 1035 2560 1440 156402029
~ Move `main_dlg_cur` `proe_win` 9 1432 960 0 1 1566 1035 2560 1440 156402032
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 1432 960 0 0 1566 1035 2560 1440 156402113
@ sel view 0
 1.889157 0.000000 0.000000 0.000000 1.889157 0.000000
 0.000000 0.000000 1.889157 477.371130 142.557044 -1675.418056 0.327680 0.000000 0
@ stack attr 8
@ stack attr -1 0  1
@ sel2d 0 TEXT_TAG 
3 4
@ stack idx 0
@SEL_REC 0 [] 14 4 -1 (0.0000000000 0.0000000000) (2692.9198957041 -522.0386131243 0.0000000000)
!Text
~ LButtonArm `main_dlg_cur` `proe_win` 9 1432 960 0 129 1566 1035 2560 1440 156402199
!Command ProCmdEditValueDim was pushed from the software.
!%CPEnter value for linear_tol_0_0 [0.3]
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 1432 960 0 256 1566 1035 2560 1440 156402349
!%TR
.2

cmdmgr_trail_output no

~ LButtonArm `main_dlg_cur` `proe_win` 9 869 692 0 1 1566 1035 2560 1440 156532967
~ Move `main_dlg_cur` `proe_win` 9 869 692 0 1 1566 1035 2560 1440 156532970
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 869 692 0 0 1566 1035 2560 1440 156533064
@ sel view 0
 1.889157 0.000000 0.000000 0.000000 1.889157 0.000000
 0.000000 0.000000 1.889157 477.371130 142.557044 -1675.418056 0.327680 0.000000 0
@ stack attr 8
@ stack attr -1 0  1
~ LButtonArm `main_dlg_cur` `proe_win` 9 1434 959 0 1 1566 1035 2560 1440 156534770
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 1434 959 0 0 1566 1035 2560 1440 156534824
@ sel view 0
 1.889157 0.000000 0.000000 0.000000 1.889157 0.000000
 0.000000 0.000000 1.889157 477.371130 142.557044 -1675.418056 0.327680 0.000000 0
@ stack attr 8
@ stack attr -1 0  1
@ sel2d 0 TEXT_TAG 
3 4
@ stack idx 0
@SEL_REC 0 [] 14 4 -1 (0.0000000000 0.0000000000) (2697.8955877896 -519.5507670815 0.0000000000)
!Text
~ LButtonArm `main_dlg_cur` `proe_win` 9 1434 959 0 129 1566 1035 2560 1440 156534906
!Command ProCmdEditValueDim was pushed from the software.
!%CPEnter value for linear_tol_0_0 [0.2]
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 1434 959 0 256 1566 1035 2560 1440 156535059
!%TR
.1

These parameters are saved in model files but not in a useful place like the .dtl detail area that would be easy to import an update.

Workaround? naw:

Spoiler

The workaround I do not want to do is abandoned all these built in parameters that are supposed to do the job and make similarly named params in every model to use. Then I would have to find and update every note that has the system parameter in it. Update all Plus the defaults in Creo that are also save in the model and can be displayed on screen will be wrong.

Can make params of the same name in the parts, what! Wow.

Spoiler

Another bad thing is users can add parameters of the same name in the model. Those user added clones work within parameters and relations but not outside of that. When using in a note (&linear...) the system parameter is shown not the user created one.

Additional note: How to display the set tol for dimension with zero decimal places

Spoiler

Additional note there is an old locked thread asking how to display the linear tol for no decimal places shown on a dimension. There is a way to set that in the config which is known with alternate input method in config.pro. 

Regular config.pro starts at one decimal place

linear_tol_0.0 0.25

Optional input method of the same setting

linear_tol 1 0.25 2

Optional input for zero decimal places

linear_tol 0 0.5 1

The way to display that in a note/title block or other location is "&linear_tol_0_"

---

Hi,

I am not sure whether you can create mapkey with requested functionality.

On the other side I think you can get requested functionality using AutoIt.

• AutoIt script can replicate actions that you now perform interactively.
• When using AutoIt you need some programming knowledge.
• The question is whether you are allowed to use AutoIt.

[BG_9869104]

Outside software is not allowed unfortunately.  

[Chris3]

Certainly not an easy way to do this but I am pretty sure you can do this with a combination mapkey and trail file. The below was done in Creo 7. You could record / edit a trail file for each one and then have a mapkey run the trail files.

Note: Trail files are notoriously finicky and often lead to Creo crashing so test test test. I have also seen cases where it is possible to lift commands out of trail files and put them into mapkeys and successfully make then run so you could try that although that may not be possible in this case.

Mapkey:

mapkey trl_0_0_tol ~ Close `main_dlg_cur` `appl_casc`;\
mapkey(continued) ~ Command `ProCmdUtilTrailTrain` ;\
mapkey(continued) ~ Trail `UI Desktop` `UI Desktop` `DLG_PREVIEW_POST` `file_open`;\
mapkey(continued) ~ Input `file_open` `Inputname` \
mapkey(continued) `C:\\Folder\\trail.txt.1`;\
mapkey(continued) ~ Update `file_open` `Inputname` \
mapkey(continued) `C:\\Folder\\trail.txt.1`;\
mapkey(continued) ~ Activate `file_open` `Inputname`;

Trail file:

!trail file version No. 1961
!Creo  TM  7.0  (c) 2021 by PTC Inc.  All Rights Reserved.
!Exit Logger data:
!	Process ID: 7176
!	Application: Creo_Parametric
!	Start date&time: 2021/10/25  06:35:28
!	language: usascii
!	machine type: x86e_win64
!	datecode: 7.0.3.0
!	Server: NONE
!	Workspace: NONE
!	traceback file: c:\traceback.log
!end Exit Logger data.
~ Open `main_dlg_cur` `Sst_bar.filter_list`
~ Close `main_dlg_cur` `Sst_bar.filter_list`
~ Select `main_dlg_cur` `Sst_bar.filter_list` 1 `5`
~ LButtonArm `main_dlg_cur` `proe_win` 9 1443 888 0 1 1556 953 1920 1200 65181
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 1443 888 0 0 1556 953 1920 1200 65275
@ stack attr 8
@ stack attr -1 0  1
@ sel2d 0 TEXT_TAG 
3 4
@ stack idx 0
@SEL_REC 0 [] 14 4 -1 (0.0000000000 0.0000000000) (1088.7657397692 57.5485309549 0.0000000000)
~ LButtonArm `main_dlg_cur` `proe_win` 9 1443 888 0 129 1556 953 1920 1200 65347
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 1443 888 0 256 1556 953 1920 1200 65361
!%TR
0.2

[MartinHanak]

---

@Chris3 wrote:

Certainly not an easy way to do this but I am pretty sure you can do this with a combination mapkey and trail file. The below was done in Creo 7. You could record / edit a trail file for each one and then have a mapkey run the trail files.

Note: Trail files are notoriously finicky and often lead to Creo crashing so test test test. I have also seen cases where it is possible to lift commands out of trail files and put them into mapkeys and successfully make then run so you could try that although that may not be possible in this case.

Mapkey:

mapkey trl_0_0_tol ~ Close `main_dlg_cur` `appl_casc`;\
mapkey(continued) ~ Command `ProCmdUtilTrailTrain` ;\
mapkey(continued) ~ Trail `UI Desktop` `UI Desktop` `DLG_PREVIEW_POST` `file_open`;\
mapkey(continued) ~ Input `file_open` `Inputname` \
mapkey(continued) `C:\\Folder\\trail.txt.1`;\
mapkey(continued) ~ Update `file_open` `Inputname` \
mapkey(continued) `C:\\Folder\\trail.txt.1`;\
mapkey(continued) ~ Activate `file_open` `Inputname`;

Trail file:

!trail file version No. 1961
!Creo  TM  7.0  (c) 2021 by PTC Inc.  All Rights Reserved.
!Exit Logger data:
!	Process ID: 7176
!	Application: Creo_Parametric
!	Start date&time: 2021/10/25  06:35:28
!	language: usascii
!	machine type: x86e_win64
!	datecode: 7.0.3.0
!	Server: NONE
!	Workspace: NONE
!	traceback file: c:\traceback.log
!end Exit Logger data.
~ Open `main_dlg_cur` `Sst_bar.filter_list`
~ Close `main_dlg_cur` `Sst_bar.filter_list`
~ Select `main_dlg_cur` `Sst_bar.filter_list` 1 `5`
~ LButtonArm `main_dlg_cur` `proe_win` 9 1443 888 0 1 1556 953 1920 1200 65181
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 1443 888 0 0 1556 953 1920 1200 65275
@ stack attr 8
@ stack attr -1 0  1
@ sel2d 0 TEXT_TAG 
3 4
@ stack idx 0
@SEL_REC 0 [] 14 4 -1 (0.0000000000 0.0000000000) (1088.7657397692 57.5485309549 0.0000000000)
~ LButtonArm `main_dlg_cur` `proe_win` 9 1443 888 0 129 1556 953 1920 1200 65347
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 1443 888 0 256 1556 953 1920 1200 65361
!%TR
0.2

---

Hi,

your trail file works well. Unfortunatelly only several tolerance values are available in bottom right corner.

[Chris3]

That's true I missed that the request was for all of the variables.

I haven't tried this but you may be able to use the same method on a drawing. Import a text file to the drawing with the variable names located at 0,0 and then change them. The trail file will record the mouse positions so it may be possible to do it that way. That gets a bit tricker though.

[BG_9869104]

Thank you for the replies so far. I may have to attempt a trail file + mapkey. I do not have my hopes up for that because the mapkey is to be made available to multiple users.

Does anyone know a different method of accessing these parameters inside of CREO in an existing part?

[pausob]

Several things come to mind:

1)  changing these linear_tol_0_0 config.pro settings will not do anything to the model.  It does not alter the tolerances of its existing dimensions.

2) have you looked into using linear_tol setting instead? (I think same issue as #1)

3) Maybe Modelcheck can help you in bringing in your legacy models to current standards.

4) It seems you need something more than hacking with mapkeys and what you get out-of-the-box with Creo.  I'd look at 3rd party add-ons such as NitroCell or Creo|SON 

5) not helpful but can't resist - maybe this is the chance to convince your company to switch to ISO standard for tolerancing 🙂

[BG_9869104]

New Hurdle

I was getting to testing trail files today. Got one making a note changing all settings, then deleting the note. Was about to start testing on other machines and then I realized I needed two decimal places for X.X ± 0.25. The default and many models are only set to have one decimal place for X.X. I can see no way to change the number of decimal places in an existing file. Have to have that in the initial file inherited from the config.pro

EX : 

linear_tol 1 0.25 2
gives X.X±0.25

I will have to learn some basics for model check setup to begin to see if model check can correct this. May look into learning some Pro Program. Maybe that can do it.   

[Chris3]

ModelCheck and Pro/Program, Toolkit, etc can only do what you can do with mouse clicks. If you can't make it happen with your mouse clicks there is nothing that these additional tools can do for you.

[BG_9869104]

The trail file to make note, edit, and delete after I am working on.

Spoiler

~ Activate `main_dlg_cur` `page_Annotate_control_btn` 1
< 2 1.361778 1924 0 0 1149 2560 0 0 1440 13
~ Activate `main_dlg_cur` `Annotate:casc116895072`
!%CPSelect LOCATION for note.
~ LButtonArm `main_dlg_cur` `proe_win` 9 164 399 0 1 1924 1149 2560 1440 12982549
** -0.085999 0.651871 2 1 1
-0.085999 0.550016 L 0 1.361777778 2
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 164 399 0 0 1924 1149 2560 1440 12982719
~ Activate `main_dlg_cur` `Model:casc28584504`
~ Trail `UI Desktop` `UI Desktop` `TrailProcessEditPasteTextEdit` \
 `&linear_tol_0_\n&linear_tol_0_0\n&linear_tol_0_00\n&linear_tol_0_000\n&linea\
r_tol_0_0000\n&linear_tol_0_00000\n&linear_tol_0_000000\n\n&angular_tol_0_\n&a\
ngular_tol_0_0\n&angular_tol_0_00\n&angular_tol_0_000\n&angular_tol_0_0000\n&a\
ngular_tol_0_00000\n&angular_tol_0_000000`
~ LButtonArm `main_dlg_cur` `proe_win` 9 215 393 0 1 1924 1149 2560 1440 12993144
@ GRM <GrmNoteBox> <Move box dragger> 1 -555.3511886398 227.0038691672 0.0000000000
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 215 393 0 0 1924 1149 2560 1440 12993197
@ GRM <GrmNoteBox> <Move box dragger> 1 151.2613621221 1536.1748803398 1038.8941586379
~ LButtonArm `main_dlg_cur` `proe_win` 9 174 401 0 1 1924 1149 2560 1440 12994669
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -593.2724100495 216.9981889836 0.0000000000
@ GRMSEL Drw_Edit_Note 0 0 0 1
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 174 401 0 0 1924 1149 2560 1440 12994741
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -78.6553524804 549.2819843342 0.0000000000
~ LButtonArm `main_dlg_cur` `proe_win` 9 174 401 0 1 1924 1149 2560 1440 12996166
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -593.2724100495 216.9981889836 0.0000000000
@ GRMSEL Drw_Edit_Note 0 0 0 1
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 174 401 0 0 1924 1149 2560 1440 12996237
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -78.6553524804 549.2819843342 0.0000000000
~ LButtonArm `main_dlg_cur` `proe_win` 9 174 401 0 129 1924 1149 2560 1440 12996494
!%CPEnter value for linear_tol_0_ [0]
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 174 401 0 256 1924 1149 2560 1440 12996512
!%TR
0
@ GRMSEL Drw_Edit_Note 0 0 0 1
~ LButtonArm `main_dlg_cur` `proe_win` 9 192 416 0 1 1924 1149 2560 1440 13010741
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -584.2921308150 198.2375386392 0.0000000000
@ GRMSEL Drw_Edit_Note 1 0 0 2
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 192 416 0 0 1924 1149 2560 1440 13010837
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -65.4373368146 538.2669712794 0.0000000000
~ LButtonArm `main_dlg_cur` `proe_win` 9 192 416 0 129 1924 1149 2560 1440 13010924
!%CPEnter value for linear_tol_0_0 [0.2]
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 192 416 0 256 1924 1149 2560 1440 13010947
!%TR
0.25
@ GRMSEL Drw_Edit_Note 1 0 0 2
!
~ LButtonArm `main_dlg_cur` `proe_win` 9 200 432 0 1 1924 1149 2560 1440 13027157
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -584.1669188889 178.2261782718 0.0000000000
@ GRMSEL Drw_Edit_Note 2 0 0 2
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 200 432 0 0 1924 1149 2560 1440 13027228
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -59.5626631854 526.5176240209 0.0000000000
~ LButtonArm `main_dlg_cur` `proe_win` 9 200 432 0 129 1924 1149 2560 1440 13027317
!%CPEnter value for linear_tol_0_00 [0.01]
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 200 432 0 256 1924 1149 2560 1440 13027337
!%TR
0.13
@ GRMSEL Drw_Edit_Note 2 0 0 2
~ LButtonArm `main_dlg_cur` `proe_win` 9 208 449 0 1 1924 1149 2560 1440 13041341
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -584.4559237437 156.9641078815 0.0000000000
@ GRMSEL Drw_Edit_Note 3 0 0 2
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 208 449 0 0 1924 1149 2560 1440 13041380
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -53.6879895561 514.0339425587 0.0000000000
~ LButtonArm `main_dlg_cur` `proe_win` 9 208 449 0 129 1924 1149 2560 1440 13041477
!%CPEnter value for linear_tol_0_000 [0.001]
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 208 449 0 256 1924 1149 2560 1440 13041496
!%TR
0.05
@ GRMSEL Drw_Edit_Note 3 0 0 2
~ LButtonArm `main_dlg_cur` `proe_win` 9 220 466 0 1 1924 1149 2560 1440 13050844
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -581.3685883876 135.7020374912 0.0000000000
@ GRMSEL Drw_Edit_Note 4 0 0 3
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 220 466 0 0 1924 1149 2560 1440 13050908
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -44.8759791123 501.5502610966 0.0000000000
~ LButtonArm `main_dlg_cur` `proe_win` 9 220 466 0 129 1924 1149 2560 1440 13050981
!%CPEnter value for linear_tol_0_0000 [0.0001]
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 220 466 0 256 1924 1149 2560 1440 13051002
!%TR
0
@ GRMSEL Drw_Edit_Note 4 0 0 3
~ LButtonArm `main_dlg_cur` `proe_win` 9 240 480 0 1 1924 1149 2560 1440 13056997
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -570.2859222667 118.1920971697 0.0000000000
@ GRMSEL Drw_Edit_Note 5 0 0 4
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 240 480 0 0 1924 1149 2560 1440 13057077
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -30.1892950392 491.2695822454 0.0000000000
~ LButtonArm `main_dlg_cur` `proe_win` 9 240 480 0 129 1924 1149 2560 1440 13057132
!%CPEnter value for linear_tol_0_00000 [0.00001]
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 240 480 0 256 1924 1149 2560 1440 13057152
!%TR
0
@ GRMSEL Drw_Edit_Note 5 0 0 4
~ LButtonArm `main_dlg_cur` `proe_win` 9 231 496 0 1 1924 1149 2560 1440 13061519
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -584.5101562369 98.1807368024 0.0000000000
@ GRMSEL Drw_Edit_Note 6 0 0 2
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 231 496 0 0 1924 1149 2560 1440 13061581
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -36.7983028721 479.5202349869 0.0000000000
~ LButtonArm `main_dlg_cur` `proe_win` 9 231 496 0 129 1924 1149 2560 1440 13061645
!%CPEnter value for linear_tol_0_000000 [0.000001]
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 231 496 0 256 1924 1149 2560 1440 13061668
!%TR
0
@ GRMSEL Drw_Edit_Note 6 0 0 2
~ LButtonArm `main_dlg_cur` `proe_win` 9 277 527 0 1 1924 1149 2560 1440 13068404
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -558.5229640218 59.4087260906 0.0000000000
@ GRMSEL Drw_Edit_Note 8 0 0 4
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 277 527 0 0 1924 1149 2560 1440 13068485
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -3.0189295039 456.7558746736 0.0000000000
~ LButtonArm `main_dlg_cur` `proe_win` 9 277 527 0 129 1924 1149 2560 1440 13068549
!%CPEnter value for angular_tol_0_ [0]
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 277 527 0 256 1924 1149 2560 1440 13068570
!%TR
2
@ GRMSEL Drw_Edit_Note 8 0 0 4
~ LButtonArm `main_dlg_cur` `proe_win` 9 280 542 0 1 1924 1149 2560 1440 13073076
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -562.2039605782 40.6480757462 0.0000000000
@ GRMSEL Drw_Edit_Note 9 0 0 4
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 280 542 0 0 1924 1149 2560 1440 13073148
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -0.8159268930 445.7408616188 0.0000000000
~ LButtonArm `main_dlg_cur` `proe_win` 9 280 542 0 129 1924 1149 2560 1440 13073214
!%CPEnter value for angular_tol_0_0 [0.5]
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 280 542 0 256 1924 1149 2560 1440 13073232
!%TR
2
@ GRMSEL Drw_Edit_Note 9 0 0 4
~ LButtonArm `main_dlg_cur` `proe_win` 9 282 559 0 1 1924 1149 2560 1440 13076550
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -567.5574757494 19.3860053559 0.0000000000
@ GRMSEL Drw_Edit_Note 10 0 0 3
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 282 559 0 0 1924 1149 2560 1440 13076621
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 0.6527415144 433.2571801567 0.0000000000
~ LButtonArm `main_dlg_cur` `proe_win` 9 282 559 0 129 1924 1149 2560 1440 13076686
!%CPEnter value for angular_tol_0_00 [0.50]
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 282 559 0 256 1924 1149 2560 1440 13076706
!%TR
2
@ GRMSEL Drw_Edit_Note 10 0 0 3
~ LButtonArm `main_dlg_cur` `proe_win` 9 284 578 0 1 1924 1149 2560 1440 13079229
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -573.7394244825 -4.3774850804 0.0000000000
@ GRMSEL Drw_Edit_Note 11 0 0 2
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 284 578 0 0 1924 1149 2560 1440 13079309
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 2.1214099217 419.3048302872 0.0000000000
~ LButtonArm `main_dlg_cur` `proe_win` 9 284 578 0 129 1924 1149 2560 1440 13079373
!%CPEnter value for angular_tol_0_000 [0.500]
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 284 578 0 256 1924 1149 2560 1440 13079392
!%TR
2
@ GRMSEL Drw_Edit_Note 11 0 0 2
~ LButtonArm `main_dlg_cur` `proe_win` 9 287 590 0 1 1924 1149 2560 1440 13083709
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -576.1777706961 -19.3860053559 0.0000000000
@ GRMSEL Drw_Edit_Note 12 0 0 2
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 287 590 0 0 1924 1149 2560 1440 13083773
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 4.3244125326 410.4928198433 0.0000000000
~ LButtonArm `main_dlg_cur` `proe_win` 9 287 590 0 129 1924 1149 2560 1440 13083860
!%CPEnter value for angular_tol_0_0000 [0.5000]
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 287 590 0 256 1924 1149 2560 1440 13083880
!%TR
2
@ GRMSEL Drw_Edit_Note 12 0 0 2
~ LButtonArm `main_dlg_cur` `proe_win` 9 287 607 0 1 1924 1149 2560 1440 13086333
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -583.2194559727 -40.6480757462 0.0000000000
@ GRMSEL Drw_Edit_Note 13 0 0 2
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 287 607 0 0 1924 1149 2560 1440 13086397
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 4.3244125326 398.0091383812 0.0000000000
~ LButtonArm `main_dlg_cur` `proe_win` 9 287 607 0 129 1924 1149 2560 1440 13086477
!%CPEnter value for angular_tol_0_00000 [0.50000]
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 287 607 0 256 1924 1149 2560 1440 13086498
!%TR
2
@ GRMSEL Drw_Edit_Note 13 0 0 2
~ LButtonArm `main_dlg_cur` `proe_win` 9 289 621 0 1 1924 1149 2560 1440 13088780
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 -587.3303208010 -58.1580160676 0.0000000000
@ GRMSEL Drw_Edit_Note 14 0 0 1
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 289 621 0 0 1924 1149 2560 1440 13088860
@ GRM <DrwEditNote> <Drw_Edit_Note> 1 5.7930809399 387.7284595300 0.0000000000
~ LButtonArm `main_dlg_cur` `proe_win` 9 289 621 0 129 1924 1149 2560 1440 13088925
!%CPEnter value for angular_tol_0_000000 [0.500000]
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 289 621 0 256 1924 1149 2560 1440 13088947
!%TR
2
@ GRMSEL Drw_Edit_Note 14 0 0 1
~ LButtonArm `main_dlg_cur` `proe_win` 9 286 723 0 1 1924 1149 2560 1440 13094965
~ LButtonDisarm `main_dlg_cur` `proe_win` 9 286 723 0 0 1924 1149 2560 1440 13095095
~ Activate `main_dlg_cur` `Model:Edit_cb_feat_delete`

[BG_9869104]

The marked solution was not by me. It is not a solution to install 3rd party software. and it does not complete the task of editing visible decimal places.

There is no solution is the solution. Feature request submitted to add linear tol settings to prt files detailing options.

I can edit the values of linear_tol_0_... with trail file run but I cannot edit the number of visible decimal places in an existing model. There is no way within standard CREO that is well known. A programmer maybe could write an addon that made the settings editable.

[pausob]

I totally agree that PTC needs to fix a number of items related to the CAD model's tolerance specification.
It seems to me that the whole process was originally based on the rigid philosophy that the tolerance standard has to be defined prior to starting the design.

The software really should be revamped to make it easy to update an existing CAD model to new tolerance specification.

As was described in this thread, after the model is constructed, changing its ANSI tolerance standard can be done by weird process of modifying the special linear_tol_0... parameters.  But to do so, one first has to make a note that calls out the display of those parameter values.  I document this in the attached video in which I also want to showcase how the tolerances on individual dimensions can be over-ridden or made unintentionally different from those in the tolerance block.  The video also shows how to "trick" the system into updating the tolerances of all nominal dimensions to be aligned with the values displayed in the tolerance block, thus making the CAD model consistent with the drawing.  Maybe this work-around is no longer necessary in later versions of Creo?  Or maybe something in my system makes it necessary; there are numerous settings that affect how tolerances are controlled in Creo and I'm not familiar with all of them.

Moreover, for the case of modifying the schemes where there are different number of digits in the tolerance value vs. in the displayed dimension value, there is no solution - unbelievably, one is forced to recreate the model and its drawing.  I thought one could do something like switch to ISO standard and then go back to ANSI standard and the new config.pro settings for the linear_tol and angular_tol parameters would be applied.... But alas, that's not the case. It seems that the Creo model "remembers" the settings for the ANSI tolerance standard even when it is switched to ISO standard and it then re-applies them when it's switched back to ANSI mode.

And speaking of ISO tolerancing method, it would be great if PTC made the tolerance_class setting into a special parameter that acts the same way as those linear_tol_0_... parameters.  That way, the tolerance class can be displayed on the drawing or in the MBD by a parametric note.  Right now, it's very easy to make the ISO models inconsistent with the drawing because the model class is indicated on the drawing's title block with a dumb static string...

[BG_9869104]

I know a lot more about the about those quirks from your post now. Thank you for that!

I tried do using "purge_history_on_save_copy" after switching to ISO. But it did not work. I opened the new file and switch to ASME and same old linear tols from the old part.

I tried "model > get data > copy from" in a new empty part but that copies everything in including the old linear tols.

I tried feature copy by selecting all the features in the tree and copy pasting that into a new empty file which I do not think is viable, but has some functionality. After redefining every feature I have one part updated. Mind you this part had no relations driving dimensions. Would have to fiddle more to see how smooth copying those in is. I have not used copy feature like this before so I might not know the trick to getting the process setup before hand to have it be a simple copy paste without and reference definition.

model > getdata > copy from is the only way I have found that moves the linear tol settings from one file to another. Not that useful in this instance.

Sliding the foundation out from under a model and forcing a new one in is obviously a challenge. It is more than needs to be done. I have a toolbox full of hammers though.