Hi,
I would like to report a bug about the new submodel option of the sixth version of Simile. The software (or I) can not manage to define without bugging a submodel with new option "Rectangular grid" and the index option "column_id()" and "row_id()". Each time (on different models) I defined a rectangular grid of several patches referred by two variables row=row_id() and col=column_id() my simile file bugs:
I can not change anything. When I click on a variable (all of them), previously defined, an error message appears "Simile encountered an unexpected problem: windows name "equation" already exists in parent" and I'm not able to change anything. Even with a single fully new model opened.
The file is just crashed.
The solution is to go back to the first submodel definition from a fixed array.
Thanks' for having a look on this bug !
Thibault M.
Comments
#1
Hi, can you try this again with the latest version please? That's Simile 6.3.
#2
This problem still occurs with version 6.3 (the popup to declare the version in this forum does not include the last version!).
Thanks for your help.
#3
I'm still failing to reproduce this problem (or your other problem)
Which version of Windows are you using?
Is your Simile installation on a remote server in a networked system, or is your home directory on a remote server?
When you get the error message, does the window have a 'More Info' button? If so, what is the info? (you should be able to copy and paste it)
Thanks for your help -- Jasper
#4
Hi,
This bug occurs when:
1. First I create an associated submodel with the submodel property "Rectangular Grid" and I define 2 varibales row and column with respectively the function row_id() and column_id(). I define some other variables. I save my model.
2. Then I double click on the model to see again the dialogue box "model property" and click on OK. Then I click on any variables and an error message appears: "Equation already exists in parents".
Details of the first alert message:
"
Simile encountered an unexpected problem:
window name "equation" already exists in parent
The error was:
window name "equation" already exists in parent
while executing
"toplevel $t -bd 4"
(procedure "PutItThere" line 3)
invoked from within
"PutItThere .equation $parent"
(procedure "create_equation" line 13)
invoked from within
"create_equation .mswindow00001.canvas init_val_for N {Dimension\ 2\ of\ \"Patch\"\ (7) Dimension\ 1\ of\ \"Patch\"\ (7)} {{rect_nbr sw s se w e nw n n..."
invoked from within
"catch $args retVal"
Press "Help" to display a relevant page from Simile's documentation."
Details of the second alert message:
"window name "mnrect_nbr" already exists in parent
window name "mnrect_nbr" already exists in parent
while executing
"menu $kname -tearoff 0"
(procedure "ClickObj" line 155)
invoked from within
"ClickObj 1022 511 .mswindow00001.canvas 1180 824 click"
("eval" body line 1)
invoked from within
"eval [list ClickObj 1022 511 .mswindow00001.canvas 1180 824 click]"
invoked from within
"if {[set gap]<500 && [set motn]<5} {
event generate [list .mswindow00001.canvas] <Button-1> -rootx 1180 -rooty 824 -x 1022 -y 511
# which will be..."
(command bound to event)".
Thanks' if you are able to do anything.
Thibault M.
#5
Thanks very much for that description, I see this happening now.
I will probably need to patch the release to fix it.
--Jasper
#6
Have found and fixed the problem. When you open the submodel properties the second time, the compass points appear in the enumerated types listbox (in the Advanced tab), which they should not because they are implicit in the rectangular grid submodel type. Thus when you OK it a second time, they are defined as a local type as well as implicitly. So they are added to the menu twice when an equation is edited, causing the error messages.
You can fix your model by deleting all the explicit occurrences of the rect_nbr type. I will make a patch release to fix the problem properly -- after I have found and also fixed the problem with '^'.
--Jasper
#7
Hi, I've patched the current release to fix this problem -- please download and reinstall, and let me know if it's OK
--Jasper
#8
Automatically closed -- issue fixed for 2 weeks with no activity.