Skip to main content
kdirth
kdirth21-Topaz I
21-Topaz I
June 14, 2019
Solved

Pinning File in Recent Files List

  • June 14, 2019
  • 2 replies
  • 3716 views

Can anyone explain why pinning a file in the recent files list does not work very well?

 

I pinned a couple of files, a few days ago, in the recent files list under the File tab, as I would do in many other programs.  Today they are no longer pinned.  Shouldn't they stay pinned until I unpin them?  I am using 4.0 and I believe the issue has been in previous versions but I wasn't frustrated enough about it to ask the question.

Best answer by kdirth

I created a support case with PTC.  With my help in understanding the issue, support services was able to recreate the problem and has SPR #8698458 with R&D.

 

Hopefully there will be a fix sometime in the near future.

2 replies

M
MartinHanak24-Ruby III
24-Ruby III
June 17, 2019

Hi,

I did some investigation ...

Recent Files List is saved in Windows Registry in HKEY_CURRENT_USER\Software\PTC\Creo_Parametric folder.


Information about "file pinning" is saved in PinnedFile variable. The variable contains the sum of "index" values. Index value = power of 2
1st file in the list has index 1 ... 2^0
2nd file in the list has index 2 ... 2^1
3rd file in the list has index 4 ... 2^2
4th file in the list has index 8 ... 2^3
and so on

 

If you open another file, existing Recent Files List moves down.

If you are able to reproduce the problem, you can report it to PTC Support.

kdirth
kdirth21-Topaz IAuthor
21-Topaz I
June 18, 2019

Doing more research, I found article CS252288, https://www.ptc.com/en/support/article?n=CS252288&source=Article%20viewer.  Same issue reported to R&D.  Resolution: Closed as not repeatable, Set config.pro visible_recent_files set to 5.

 

Experimenting more with the pinning of files, I believe the issue is in the fact that the pinned files are not moved to the top of the list as they are in MS Office.  It appears that when the pinned file drops below the visible limit of 30, it disappears, with no regard to the config setting.  This also reduces the number of visible files from the config setting.  My config setting is currently 20, I only see 17 because I forced 3 pinned files below the limit of 30.

There is always more to learn.
M
MartinHanak24-Ruby III
24-Ruby III
June 19, 2019
@kdirth wrote:

Doing more research, I found article CS252288, https://www.ptc.com/en/support/article?n=CS252288&source=Article%20viewer.  Same issue reported to R&D.  Resolution: Closed as not repeatable, Set config.pro visible_recent_files set to 5.

 

Experimenting more with the pinning of files, I believe the issue is in the fact that the pinned files are not moved to the top of the list as they are in MS Office.  It appears that when the pinned file drops below the visible limit of 30, it disappears, with no regard to the config setting.  This also reduces the number of visible files from the config setting.  My config setting is currently 20, I only see 17 because I forced 3 pinned files below the limit of 30.

Hi,

you are right, pinned files are not located at the top of the list. This means that "pinned" function is poorly implemented. To see pinned files at the top of the list, you have to develop your own "pinned" function outside of Creo.

For example:

  • in startup directory you create special file containing absolute file paths
  • you develop special Creo starting procedure which
    • reads this special file
    • reads the contents of HKEY_CURRENT_USER\Software\PTC\Creo_Parametric folder in Windows Registry 
    • combines two above information sources into one and imports the result back into Windows Registry

 

kdirth
kdirth21-Topaz IAuthorAnswer
21-Topaz I
June 21, 2019

I created a support case with PTC.  With my help in understanding the issue, support services was able to recreate the problem and has SPR #8698458 with R&D.

 

Hopefully there will be a fix sometime in the near future.

There is always more to learn.
kdirth
kdirth21-Topaz IAuthor
21-Topaz I
July 11, 2019

R&D reported they were unable to recreate the issue.  I gave them a simple 3 step process to create the issue I was seeing and they were able to recreate the issue.  Now we wait for a solution to be implemented.

There is always more to learn.
kdirth
kdirth21-Topaz IAuthor
21-Topaz I
July 30, 2019

Here is the final answer that I received:

 

R&D has planned to fix this issue in Creo Parametric 4.0 M110. As there is not further releases for Creo Parametric 5.0, this will not be fixed in Creo Parametric 5.0 version.

There is always more to learn.
Terms & ConditionsAccessibility statement