Re: [Scilab-users] Rép : Problems with figures in Scilab 6.0.0

[Samuel Gougeon]

http://mailinglists.scilab.org/Scilab-users-Problems-with-figures-in-Scilab-6-0-0-tt4036346.html

Hello Philippe,
The screenshot looks normal to me: lines are continuous and of minimal 
thickness, what is the default and standard. Since there is no 5.5 
output to be compared (*), i would say that all this is normal.
You could check that the attributes for the fonts size have their 
default standard values.


If you use some external toolboxes, may be one of them had changed the 
default values through gda().

Otherwise, you can use gda() to do so according to your wishes.

Regards
Samuel

(*) AFAIK, at least on Windows, there is no need to uninstall a Scilab 
release to install a new one, or as many versions needed. Hence, we 
never have to abandon a known working environment to get a new one: we 
can have all of them together.


Le 11/05/2017 à 11:53, Philippe Dérogis a écrit :

Hi Samuel,

  Find in here https://we.tl/QIICI7f19C a capture of the figure window 
with scilab 6.0. I tried to reinstall scilab 5.5 in order to provide 
you with the capture of the same figure generated with scilab 5.5 but 
it doesn’t worked. I remember that at some point I had to do a strange 
things such as overwriting some system libraries in order to have 
scilab working (I founded the fix on the internet) but I didn’t 
remember what. So unfortunately the capture of the 6.0 figure is the 
only thing that I can give you.


Thanks for your help.

Philippe.


___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

[Scilab-users] VIM syntax script for Scilab 6 ?

[Erhy]

Hello,
has anybody an actual syntax script  for Scilab 6 ?
Mine doesn't care to comments in /* */ in .sce files.
Thank you
Erhy



--
View this message in context: 
http://mailinglists.scilab.org/VIM-syntax-script-for-Scilab-6-tp4036390.html
Sent from the Scilab users - Mailing Lists Archives mailing list archive at 
Nabble.com.
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] surf and plot3d

[Jens Simon Strom]

Thanks a lot, Patrice!
Regards, Jens
--
Am 15.05.2017 11:10, schrieb Patrice MEGRET:


Dear Jens,

If you use plot3d instead of surf, it is ok.

The problem is that surf uses Matlab definition of the matrix Z 
whereas plot3d, ... use Scilab definition. èthere is a transposition 
between these two definitions (see help file)


Ndgrid for plot3d, contour, ...

Meshgrid for surf

If you would like to use surf with ndgrid: surf(x,y,Z.')

PM

*De :*users [mailto:users-boun...@lists.scilab.org] *De la part de* 
Jens Simon Strom

*Envoyé :* dimanche 14 mai 2017 18:51
*À :* International users mailing list for Scilab. 


*Objet :* [Scilab-users] surf and plot3d

Hi,
Please check the graph below:
  
x=[0  1]; y=[0  2];

[X,Y]=_ndgrid_(x,y)
Z=X+2*Y
xdel();
_surf_(x,y,Z)
param3d(X,Y,Z)
ce=_gce_();   ce.line_mode="off";   ce.mark_mode  =  "on";   ce.mark_size  =  10
ca=_gca_(); ca.rotation_angles=[65  290];
  
The facet corners do not coincide with the marks in Version 5.4.0. and 5.5.2.. Shouldn't they?
  
Kind regards

Jens


___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users


___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] surf and plot3d

[Patrice MEGRET]

Dear Jens,

If you use plot3d instead of surf, it is ok.

The problem is that surf uses Matlab definition of the matrix Z whereas plot3d, 
... use Scilab definition. ==> there is a transposition between these two 
definitions (see help file)

Ndgrid for plot3d, contour, ...
Meshgrid for surf

If you would like to use surf with ndgrid: surf(x,y,Z.')

PM




De : users [mailto:users-boun...@lists.scilab.org] De la part de Jens Simon 
Strom
Envoyé : dimanche 14 mai 2017 18:51
À : International users mailing list for Scilab. 
Objet : [Scilab-users] surf and plot3d


Hi,

Please check the graph below:



x=[0 1]; y=[0 2];

[X,Y]=ndgrid(x,y)

Z=X+2*Y

xdel();

surf(x,y,Z)

param3d(X,Y,Z)

ce=gce();   ce.line_mode="off";   ce.mark_mode = "on";   ce.mark_size = 10

ca=gca(); ca.rotation_angles=[65 290];



The facet corners do not coincide with the marks in Version 5.4.0. and 5.5.2.. 
Shouldn't they?



Kind regards

Jens
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users

Re: [Scilab-users] linking (jumping) from line of code to an other

[Frieder Nikolaisen]

 

Dear Tim, 

thanks for your answer. I have already the trouble of
handling the code from last autum. In the moment I have written my exam,
my boss has the trouble all to himself. 

I will still use your advice.
Unfortuanlly I had to learn in a few weeks coding on myself. It's surely
easy to see by reading the code. 

Best regards
Frieder 

Am 2017-05-12
18:50, schrieb Tim Wescott: 

> Jumps are generally bad style; I don't
know if Scilab even supports
> them. If it does I advise you not to use
them for something this
> trivial (error handling is the only place I've
seen them seriously
> recommended, and even there they can be very
problematical -- it's why
> people invented exceptions).
> 
> For
something that small the cost in making your code into spaghetti is
>
larger than the cost of just doing it.
> 
> The two ways that software
professionals would deal with this are to
> either get rid of 100 as a
"magic number" and assign its value to a
> variable (i.e., before the
"for" statement assign PowerIncrement =
> 100), or rearrange the
conditional so that the P = P + PowerIncrement
> line is only
encountered once.
> 
> Or do both.
> 
> Certainly if you use the
existing structure and if the two lines that
> increment P are supposed
to do the same thing always, then using a
> named variable is a Good
Thing -- that means that at some later date,
> when some poor ignorant
fool reads your code they don't have to wonder
> if the "P+100" in one
spot means the same thing as the "P+100" in
> another, AND they don't
run the risk of changing the (hopefully proper)
> increment in one place
but not another.
> 
> And note, based on my experience writing software
for the last 40
> years, that often the poor ignorant fool who has to
maintain your
> software is you, months or years down the road -- so it
pays to make
> your code readable. Nothing makes you feel dumber than
not being able
> to understand your own code, because no matter which
way the blame
> flies, it always lands squarely on you.
> 
> On Fri,
2017-05-12 at 11:15 +0200, Frieder Nikolaisen wrote:
> 
>> Hello,
another question to solve the locomotive stuff, giving you a example
with the not implented code. I don't want to code the same stuff twice.
Thats why I want to jump between lines of code. Is this possible and
how? P = 200; DM = 1; for n = 1:10 if DM == 1 then if P > 100 then DM =
1 P = P - 60 disp('P bigger 100. DM = ' + string(DM)) else DM = 0 P = P
+ 100 //instead of writing P = P + 100, I would like ... disp('P smaller
100. DM = ' + string(DM)) end else // D == 0 if P > 100 then DM = 1
disp('P bigger 100. DM = ' + string(DM)) P = P - 30 else DM = 0 // ...
to continue here disp('P smaller 100. DM = ' + string(DM)) P = P + 100
// to use this P = P + 100 end end disp(string(n) + ' ' + string(P)) end
___ users mailing list
users@lists.scilab.org [1]
http://lists.scilab.org/mailman/listinfo/users [2]

 

Links:
--
[1]
mailto:users@lists.scilab.org
[2]
http://lists.scilab.org/mailman/listinfo/users
___
users mailing list
users@lists.scilab.org
http://lists.scilab.org/mailman/listinfo/users