-- Bug description --I just installed Scilab 4.1.2 I have a problem when I try to use the Scipad. When I try to save a file (any file!) as a "Scilab File" the program just crashes. When I save it as a "Scicos File" it does not crash. However when I then execute it from the scipad (with F5) it runs but then crashes. When I close the scipad and just run it from the console using Exec.. it runs normal. I have no idea how this can be caused. I'm using Windows Vista Home Premium, and like I said, I use Scilab 4.1.2. The program gives no error message, it just doesn't respond anymore.-- Scilab error message ---- How to reproduce the bug --
Designs
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related or that one is blocking others.
Learn more.
"the program just crashes"
"The program gives no error message, it just doesn't respond anymore"
Could you be more specific about what is crashing exactly? Scipad? Scilab?
Both?
I have to say that technically from Scipad there is absolutely no difference
if you save your file as a Scilab file or as a Scicos file. This is handled in
Tcl/Tk on which Scipad is built, not in Scipad itself.
I can't test in your exact case since I don't own your non free OS...
When you select "Save as..." from the file menu of Scipad, the file selection
box opens, right? Then you type a filename and select the type of the file in
the combobox, still right? Then Scipad crashes instantaneously and with no
error message when you click on OK in that dialog, can you confirm that?
Francois
PS: "All OS" setting in this bug report corrected to "Windows 2000 and more"
I have the same problem, and found this thread upon querying the list of bugs.
I am running 32-bit Vista Business. When I open Scipad and try to save the
current file with any name besides "untitled.sce", scipad hangs. If I click on
the console window and click back to the editor, Scipad unhangs, but the
filename on scipad doesn't reflect the new filename I tried to enter. Then, if
I try to close Scipad OR the console by clicking the upper-right-hand X, it is
unresponsive. No error messages are generated and there is no prompt to log the
error.
OK, since the original poster didn't answer my post above, are you ready,
Kevin, to help me in fixing this bug?
I would ask you some questions and also you would have some tests to perform.
I don't have Vista and I have no intention to buy it, be it for fixing Scipad
bug.
Sorry that I didn't reply Francois, I'm very busy right now. I hope you and
Kevin can fix the bug together. I confirm your desciption of the bug by the way.
I have the same problem running Vista 32 and Vista 64. Love Scilab in XP but
times change and had to move to Vista.
"When I open Scipad and try to save the
current file with any name besides "untitled.sce", scipad hangs. If I click on
the console window and click back to the editor, Scipad unhangs, but the
filename on scipad doesn't reflect the new filename I tried to enter."
in all tk_getOpenFile and tk_getSaveFile instructions.
Before committing this change, I would like to get confirmation from those who
see this bug that my changes above also fix the problem on their machines.
Please provide feedback here.
Francois
PS: Yes I know, there is another tk_getOpenFile in scilabexec.tcl (proc
importmatlab), but let's first confirm the above.
The problem doesn't happen in Vista with scilab-5.0-alpha2, which ships with
Tcl/Tk 8.4.18.
Not sure my above proposal (comment #9) should be committed.
The -parent option in tk_get*File is here to make the scipad window the
logical parent of the file open/save dialog. The file dialog is displayed on
top of its parent window, and this is desirable and intentional.
With -parent $pad, no action can be done in Scipad before closing the file
dialog. Without this option I can imagine a number of side effects if the user
is nasty.
I'm wondering if we shouldn't just make no change at all to the scipad
codebase, based on the observation that it works OK with recent Tcl/Tk
versions, and leave the workaround here for users to make their changes
themselves if they want to stick to Scilab-4.1.2 and Tcl/Tk 8.4.15.