[GiDlist] Problemtype transform and Dirty flag
Posted: Fri Oct 24, 2003 2:03 pm
Hello:
I have two questions:
1- is there a way to control what happens when we use the "problemtype |
tranform" command? What happens is the following. Let's say that I had a
boundary condition defined with one field in one version of my
problemtype. Now, in a newer version, I have two fields for the same
boundary condition. The "normal" transformation procedure in GiD (which, by
the way, is a very nice feature of the program) is such that it will lose
the boundary condition ("differences found").
I would like to force GiD to directly assign the newer definition in place
of the older one when I transform the model. In short, I would like to
define a correspondence table (old fields to new fields). Is that feasible?
Note that the same issue arises with material definitions.
2- There must be a dirty flag somewhere indicating whether or not the
current model has been modified by the user. However, I have not found how
to access/test this flag.
Thanks!
Philippe
I have two questions:
1- is there a way to control what happens when we use the "problemtype |
tranform" command? What happens is the following. Let's say that I had a
boundary condition defined with one field in one version of my
problemtype. Now, in a newer version, I have two fields for the same
boundary condition. The "normal" transformation procedure in GiD (which, by
the way, is a very nice feature of the program) is such that it will lose
the boundary condition ("differences found").
I would like to force GiD to directly assign the newer definition in place
of the older one when I transform the model. In short, I would like to
define a correspondence table (old fields to new fields). Is that feasible?
Note that the same issue arises with material definitions.
2- There must be a dirty flag somewhere indicating whether or not the
current model has been modified by the user. However, I have not found how
to access/test this flag.
Thanks!
Philippe