[GiDlist] Problemtype transform and Dirty flag

[Philippe Bouchilloux]

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

[Ramon Ribó]

Hello,

1. We are improving the transform function in GiD. The last betas
should have some improvements over the GiD 7. There is some
room to improve, yet.


2. .central.s GIDModifiedFileFlag Set | Get

Use with care. If you call it when loading the problemtype, it
is not so easy to make it work ok. As always, check what last RamSeries
do to solve the problem.

Regards,

--
Compass Ing. y Sistemas Dr. Ramon Ribo
http://www.compassis.com ramsan at compassis.com
c/ Manuel Girona, 61 bajos tel. +34 93 204 10 82
08034 Barcelona, Spain fax. +34 93 204 19 09

-----Mensaje original-----
De: gidlist-admin at gatxan.cimne.upc.es
[mailto:gidlist-admin at gatxan.cimne.upc.es] En nombre de Philippe
Bouchilloux
Enviado el: viernes, 24 de octubre de 2003 14:57
Para: GiDList
Asunto: [GiDlist] Problemtype transform and Dirty flag


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



_______________________________________________
GiDlist mailing list
GiDlist at gid.cimne.upc.es
http://gid.cimne.upc.es/mailman/listinfo/gidlist

[Philippe Bouchilloux]

Ramon:

Thanks for the info. The reason for checking GIDModifiedFileFlag is that
it is possible (Ver 7.2) to use the Calculate command after some changes
have been made in the model, even if these changes are not saved. So, if a
problem occurs during the calculation, there could be discrepancies between
the model and the results, or the changes could be simply lost.
I would like to force the user to save the model before starting the
computation.

Regards,

Philippe


2. .central.s GIDModifiedFileFlag Set | Get

Use with care. If you call it when loading the problemtype, it
is not so easy to make it work ok. As always, check what last RamSeries
do to solve the problem.