[GiDlist] On the object creation again

Moderator: GiD Team

Post Reply
Andrea Calaon

[GiDlist] On the object creation again

Post by Andrea Calaon »

Hello everyone,

in order to be able to reset the previous option of
"UseMoreWindows" I need to store the standard variable
value the user is working with. Therefore I guess I should
access the global variable ChangeVarInfo(UseMoreWindows).
But even if the variable is changed to 0 or no, the behaviour
of GiD remains unchanged and windows are used to interact
with the user. I tried the following two expressions:

global ChangeVarInfo
set ChangeVarInfo(UseMoreWindows) 0

global ChangeVarInfo
set ChangeVarInfo(UseMoreWindows) no

This on the contrary works:

.central.s process Utilities variables UseMoreWindows 0

Which is the difference between the three expressions?

Thanks

Best Regards

Andrea
Martin Meiler

[GiDlist] On the object creation again

Post by Martin Meiler »

Hello Andrea,

while greping the gid/scripts directory for

ChangeVarInfo(...)


i found only entries that had the Name

set ChangeVarInfo(Usemorewindows) yes | no | beginner

maybe that's the solution, if the switch/case statement is case-sensitive.



You can even use

central.s disable windows 'value'
The value 0/1 Enable/Disable Windows (GiD displays, or not, windows which require
interaction with the user)

EXAMPLE to disable the interaction windows:


.central.s disable windows 1


to control the apperance of user interaction windows.


good luck. maybe you can post the result of your test.


Thanks in advance

Best Regards

Martin







Andrea Calaon wrote:
Hello everyone,

in order to be able to reset the previous option of
"UseMoreWindows" I need to store the standard variable
value the user is working with. Therefore I guess I should
access the global variable ChangeVarInfo(UseMoreWindows).
But even if the variable is changed to 0 or no, the behaviour
of GiD remains unchanged and windows are used to interact
with the user. I tried the following two expressions:

global ChangeVarInfo
set ChangeVarInfo(UseMoreWindows) 0

global ChangeVarInfo
set ChangeVarInfo(UseMoreWindows) no

This on the contrary works:

.central.s process Utilities variables UseMoreWindows 0

Which is the difference between the three expressions?

Thanks

Best Regards

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




--
--------------------------------------------------------------------

_/ _/_/ _/_/_/ Friedrich Alexander Universität Erlangen
_/ _/ _/ _/ Lehrstuhl für Sensorik
_/ _/ _/ Paul-Gordanstr. 5, 91052 Erlangen, Germany
_/ _/_/ _/_/
_/ _/ _/ University of Erlangen
_/ _/ _/ _/ Department of Sensor Technology
_/_/_/ _/_/ _/_/_/ Paul-Gordanstr. 5, 91052 Erlangen, Germany


Dipl.-Ing. Martin Meiler

tel.: (+49)-9131-85-23140
fax.: (+49)-9131-85-23133

email: Martin.Meiler at lse.eei.uni-erlangen.de
User avatar
escolano
Posts: 1961
Joined: Sun Sep 05, 1982 10:51 pm

[GiDlist] On the object creation again

Post by escolano »

Hello Andrea & Martin,

To avoid to open popup windows, must set the GiD variable UseMoreWindows to 0
with
.central.s process Utilities variables UseMoreWindows 0
or
GiD_Process Utilities variables UseMoreWindows 0
(they are similar, but I recommend you to use GiD_Process)

This command change an internal variable (of the C/C++ kernel)

ChangeVarInfo(UseMoreWindows) is a Tcl/Tk global variable used to temporary store the value of UseMoreWindows.
When you open the preferences window, ChangeVarInfo(UseMoreWindows) is set to the internal value, and when you press the Accept button the internal value is set to the current ChangeVarInfo(UseMoreWindows) value.

For your problemtype, can use your own Tcl global variable to store the previous state, for example:

#save the current value and set a new value
global BeasyPriv
set BeasyPriv(UseMoreWindows) [GiD_Info variables UseMoreWindows]
GiD_Process Utilities variables UseMoreWindows 0
...
#restore the old value
global BeasyPriv
GiD_Process Utilities variables UseMoreWindows $BeasyPriv(UseMoreWindows)

Valid UseMoreWindows values are: Create new point: 0==always 1==ask -2==never

Usually, if you provide to GiD the answer in the same line, then the user won't be asked, and then it's not necessary to deactivate windows.


Can also use this Tcl commands to temporary deactivate redraws, and messages:
GidUtils::DisableGraphics
GidUtils::EnableGraphics

Regards
Enrique Escolano

----- Original Message -----
From: "Andrea Calaon" andrea at beasy.com
To: gidlist at gatxan.cimne.upc.edu
Sent: Tuesday, June 28, 2005 2:20 PM
Subject: [GiDlist] On the object creation again


Hello everyone,

in order to be able to reset the previous option of
"UseMoreWindows" I need to store the standard variable
value the user is working with. Therefore I guess I should
access the global variable ChangeVarInfo(UseMoreWindows).
But even if the variable is changed to 0 or no, the behaviour
of GiD remains unchanged and windows are used to interact
with the user. I tried the following two expressions:

global ChangeVarInfo
set ChangeVarInfo(UseMoreWindows) 0

global ChangeVarInfo
set ChangeVarInfo(UseMoreWindows) no

This on the contrary works:

.central.s process Utilities variables UseMoreWindows 0

Which is the difference between the three expressions?

Thanks

Best Regards

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listas.cimne.upc.edu/pipermail/gidlist/attachments/20050628/d4293150/attachment.htm
Post Reply