[scilab-Users] Scilab 5.3.0 x 64 bit, not visible results or error messages

[Mathieu Dubois]

Hello,

If I understand your problem you have typed a script in scinotes and 
executed it, right?

First, output is usually done in the scilab console (the window that is 
opened when you launch scilab).
You can dock scinotes and the console in the same window.
I think that, starting from scilab 5.3, your configuration is saved so 
if you dock them one time it will be restored on the next startup.

Second you can set the execution verbosity level. See help("mode").

Generally, lines ending with a semi-colon (;) are not displayed.

Hope that helps.
Mathieu

Le 19/01/2011 16:37, dr.w.grabellus at t-online.de a écrit :
> Good afternoon,
>
>
>
> before trying Scilab,  I used Matlab occasionally. Trying to get started
> with Scilab the following problem arose:
>
>
> 1. Scilab was started without problems and displayed the Scilab Console.
>
>
> 2. SciNotes were opened by pressing the SciNotes symbol,
>
>
> 3. A tested, correct script was written on SciNotes.
>
>
> 4. The script was correctly saved as cse file.
>
>
> 5 The triangular shaped push button of the SciNotes top line was pressed
> to execute the script.
>
>
> 6. Nothing happended, neither the result nor error message were displayed.
>
> However, in case the script produced a Graph, the result was displayed
> in it's own opened window.
>
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>
> What happened:
>
>
> 1. Different to the default split Matlab display, Scilab did not show
> the script and it's result or error messages on a default split
>
>    monitor. The script display on the SciNotes did completely cover the
> existing result or error messages on the Scilab
>
>    Console.
>
>
> 2. I solved this problem by reducing the Scilab Console- and SciNotes
> display, each half of the monitor size, and operate now
>
>    both on one screen.
>
>
> 3. I'm sure there will be a better solution, but this will do it for a
> while.
>
>
>
> regards
>
>
> W. Grabellus
>
>