[GiDlist] Possible Bug Reports - GiD 10.0.4

GiDList Archive 2013 - 2005
1

Hey GiD,



I noticed few bugs in the previous version, but thought they will be fixed
in the next version. I think they are still there, so thought may be a good
idea to bring them to your notice. I hope I am not doing anything wrong to
cause those bugs. I am using GiD 10.0.4 x32.


\

  •      In post-process, clicking on the "Units:" button in the standard

toolbar causes an error. I get the following error:








\

  •      Also, if I click on the "stack trace" on such errors, the stack

error window is hidden at the back of GiD windows. I have to minimize GiD
all the time and then bring the stack error window to the front. For while,
I didn’t know where the stack trace window was. It might be a good idea to
raise it to the foreground




\

  •      In the bas file I define "*messagebox error:" for certain

conditions. Whenever the error is triggered, the info window is in the front
and the error message window is hidden behind the info window. Now, the info
window is completely frozen as I guess, GiD is waiting the error window to
be closed first. It’s not possible to access or even see the error window as
it is completely behind the info window. I used to kill the GiD process for
a while, then I realized pressing “enter” on keyboard closes the error
window at the back and then GiD is normal again.



It might be a good idea to bring the error window to the foreground.







(This window is inactive and can’t be closed or moved as the error window is
behind this)





Thanks and have a nice day!











-------------- next part --------------
An HTML attachment was scrubbed…
URL: http://listas.cimne.upc.edu/pipermail/gidlist/attachments/20101112/d88965e9/attachment-0001.htm
-------------- next part --------------
A non-text attachment was scrubbed…
Name: not available
Type: image/png
Size: 10094 bytes
Desc: not available
Url : http://listas.cimne.upc.edu/pipermail/gidlist/attachments/20101112/d88965e9/attachment-0001.png
-------------- next part --------------
A non-text attachment was scrubbed…
Name: not available
Type: image/jpeg
Size: 10857 bytes
Desc: not available
Url : http://listas.cimne.upc.edu/pipermail/gidlist/attachments/20101112/d88965e9/attachment-0001.jpeg

2

Hello Shiram,

We didn’t know this bug when pressing “Units:” button in postprocess,
The solution is very simple, only edit StatusLabel.tcl and change ‘columspan’ by ‘columnspan’,
Next official and beta versions will be fixed

About the other comments, we know that some popup windows, like the “stack trace” is hidden at the back, and is difficult to be shown (minimizing/maximixing other windows),
but we don’t have any good solution nowadays.
We tried to set the -topmost flag (on Windows platforms), but the solution is worst than the problem, as you noticed, some window could be forced to appear in front (like error messages window, or help window),
but maybe other windows are raised hidden on the back, but with the focus, and the program seems locked (althought usually it is possible to use the keyboard, with escape, enter, etc to close them)

Concluding, for next versions we are avoiding this -topmost flag, is is better to have some message window hidden on the back.
Off course we will try to find a better solution… (we tried to use Tk commands like “raise”, “focus”, etc, to send to front this windows unsuccessfully)

Enrique

----- Original Message -----
From: Shriram
To: gidlist at listas.cimne.upc.edu
Sent: Friday, November 12, 2010 5:22 PM
Subject: [GiDlist] Possible Bug Reports - GiD 10.0.4


Hey GiD,



I noticed few bugs in the previous version, but thought they will be fixed in the next version. I think they are still there, so thought may be a good idea to bring them to your notice. I hope I am not doing anything wrong to cause those bugs. I am using GiD 10.0.4 x32.


\

  •      In post-process, clicking on the "Units:" button in the standard toolbar causes an error. I get the following error:









\

  •      Also, if I click on the "stack trace" on such errors, the stack error window is hidden at the back of GiD windows. I have to minimize GiD all the time and then bring the stack error window to the front. For while, I didn't know where the stack trace window was. It might be a good idea to raise it to the foreground





\

  •      In the bas file I define "*messagebox error:" for certain conditions. Whenever the error is triggered, the info window is in the front and the error message window is hidden behind the info window. Now, the info window is completely frozen as I guess, GiD is waiting the error window to be closed first. It's not possible to access or even see the error window as it is completely behind the info window. I used to kill the GiD process for a while, then I realized pressing "enter" on keyboard closes the error window at the back and then GiD is normal again.




It might be a good idea to bring the error window to the foreground.







(This window is inactive and can’t be closed or moved as the error window is behind this)





Thanks and have a nice day!












\


\

GiDlist mailing list
GiDlist at listas.cimne.upc.edu
http://listas.cimne.upc.edu/cgi-bin/mailman/listinfo/gidlist
-------------- next part --------------
An HTML attachment was scrubbed…
URL: http://listas.cimne.upc.edu/pipermail/gidlist/attachments/20101112/1af42c8b/attachment-0001.htm
-------------- next part --------------
A non-text attachment was scrubbed…
Name: not available
Type: image/png
Size: 10094 bytes
Desc: not available
Url : http://listas.cimne.upc.edu/pipermail/gidlist/attachments/20101112/1af42c8b/attachment-0001.png
-------------- next part --------------
A non-text attachment was scrubbed…
Name: not available
Type: image/jpeg
Size: 10857 bytes
Desc: not available
Url : http://listas.cimne.upc.edu/pipermail/gidlist/attachments/20101112/1af42c8b/attachment-0001.jpeg