This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ADDIDENTS like PIPES
18-02-2017, 11:58 AM, (This post was last modified: 21-02-2017, 02:10 AM by Bas.)
#1
ADDIDENTS like PIPES
If you modelled some ADDIDENTS you have to be careful when changing, for example, a bend radius in the POLYDIF table.

The position of the ADDIDENT can change.

When you can model ADDIDENTS relative to other POLYDIF points (=IDENTS), like you can with PIPES, you don't have to worry about that.
Reply
11-03-2017, 11:25 PM,
#2
RE: ADDIDENTS like PIPES
I agree with Bas.
Reply
12-07-2017, 10:07 AM,
#3
RE: ADDIDENTS like PIPES
With the upcoming new version of Ple4Win, definition of additional identifiers will be different:
A "reference identifier"-column will then be part of the ADIDENT table.
If in a data-row an existing identifier is entered in that field, the additional identifier is placed relative to that reference identifier.
If that field is left empty, identifier are placed as with the current version of the program.

So that should very much cover your request.
Note that additional identifiers are still placed on the nearest node, so the exact position might be slightly different from what was entered in ADIDENT.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)