Skip to main content
Sep 22, 2015 4:17 PM UTC
Acknowledged

Improve Relations Editor

Related products:Creo Parametric

Some of the biggest changes that need to be done:

  1. Use a color coded syntax editor right there in the relations.  Currently each user can export them, and then customize using a text editor such as Notepad++.  Although some users ( Edit Creo Relations with Notepad++ instead of the default editor ) have worked on this and actually made some substantial progress for the basics, it would be much more useful if PTC built it into the software as well as expanded on the visual display/capabilities.
  2. Improve debugging to better point to errors and more focused troubleshooting

Above are some basic bare minimum improvements to get the relations editor out of the 1980's DOS mentality.  A more advanced feature improvement to make the editor a lot more useful would be to provide dropdown menus as you type such as Excel or Visual Basics does. For example, Excel shows the syntax of each function which dramatically improves how fast people can learn and write useful code/formulas (from years to hours).

8 replies

Sep 22, 2015 4:36 PM UTC
Sep 22, 2015 5:17 PM UTC

Hey, I'd even be tickled pink if they would just start using a monospaced font and format the code using some config.pro settings (e.g., indent "if" statements x number of spaces, etc.).  Syntax highlighting would put me in a state of euphoria.  Debugging aids and tooltips -- well, I don't dare even hope.  I've asked only for a monospaced font for years to no avail.  You'd think PTC's programmers would understand the need.

I'll keep my fingers crossed.  Hope springs eternal.

LawrenceSAuthor
Sep 22, 2015 7:43 PM UTC

You would think!  I can only imagine that the programmers want this but it doesn't make the budget, or the programmers barely consider the relations editor programming and think it is to simple to give it their time?  Or perhaps they just don't use it and realize the significance...You got me why they haven't touched this.

Dec 2, 2015 4:14 PM UTC

Very good idea Lawrence.

I'm new with relations, I was about to create an idea similar to yours.

I think it's really difficult when you have a lot of relations to control the behaviour of the model, especially when you handle with IF statements.

It would be good to have a kind of highlighting for IF statements to focus better only on the relations considered at the current regeneration and a "relation tree" with levels. A very quick and simple solution is to allow the following:

1. IF ...

1. (RELATION)

1. (RELATION)

     a.IF ...

     a.(RELATION)

     a.ENDIF

     b.IF ...

     b.(RELATION)

     b.ENDIF

1.ENDIF

2. IF ...

2. (RELATION)

2. (RELATION)

     a.IF ...

     a.(RELATION)

     a.ENDIF

     b.IF ...

     b.(RELATION)

     b.ENDIF

2.ENDIF


Where is highlighted somehow the relations considered for the regeneration of the model: "2-b"

In my opinion, this can be a good start for a good job.

LawrenceSAuthor
Dec 2, 2015 4:36 PM UTC

Thanks Francesco!  In case you haven't tried using Notepad++ with the custom language definition (the link in my idea), then I highly suggest it.  It is absolutely no replacement for PTC giving us a Relations editor that is useful.  It is something, however, and in this case something is better than the nothing that PTC has thus given us.  It is not what we are looking for but it does make it less painful.  What else are we going to do when the developer hasn't done any developing in the last 20+ years?  Hopefully PTC is in the process of improving this, although I haven't heard anything...

Feb 8, 2018 3:07 PM UTC

Improving should also consist of adding reasonable helpful functions.

Right now I am doing this for getting a decimal number with a defined number of digits:

 

messwert=distance
messwert_nachkomma = itos((messwert-FLOOR(messwert))*100)
if messwert_nachkomma != ""
 messwert_nachkomma = "," + messwert_nachkomma
endif
text_distance = itos(floor(messwert)) + messwert_nachkomma

This is totally ridiculous!

I can't believe there is no better way in 2018 to do this...

 

Jun 14, 2018 7:33 PM UTC
Status changed to: Acknowledged
LawrenceSAuthor
Feb 17, 2025 1:35 PM UTC

The problem with an idea like this is how to get traction with purely the number of votes.  If an organization has 300 users, it might be that only 1 or 2 people ever deal with this, yet it sometimes affects most of the Creo users in an organization because those 1-2 people write the code and everyone else uses it.  The easier it is to write the code the better the code will be and the easier it is for everyone in the organization.

 

I wish that at least PTC could mark this as an admin category and then score it differently based on the number of users it affects.  Actually, that would be very interesting if the creator and every person who votes could specify how many people in their org that it affects in the organization.