Thanks. I runed you example. In the case of .jpg everything is fine.

But for .eps I got again the borders.

I runed the same code:

myPlot2:= plot(sin(x), x= 0..10, color= black, scaling= constrained, view= [0..10, -5..5]):
plotsetup(
  ps,
  plotoptions= `noborder,width=5cm,height=5cm`,
  plotoutput= "myPlot2.eps"
);
plots[display](myPlot2);
plotsetup(default);

and the picture that I got still with borders :(

How can it be?

p.s. I am using Maple 11.

Here my result:

<a href='http://www.mapleprimes.com/files/8091_myPlot2.eps'>myPlot2.eps</a>

Thanks. I runed you example. In the case of .jpg everything is fine.

But for .eps I got again the borders.

I runed the same code:

myPlot2:= plot(sin(x), x= 0..10, color= black, scaling= constrained, view= [0..10, -5..5]):
plotsetup(
  ps,
  plotoptions= `noborder,width=5cm,height=5cm`,
  plotoutput= "myPlot2.eps"
);
plots[display](myPlot2);
plotsetup(default);

and the picture that I got still with borders :(

How can it be?

p.s. I am using Maple 11.

Here my result:

<a href='http://www.mapleprimes.com/files/8091_myPlot2.eps'>myPlot2.eps</a>

There below the college had the same error :( http://2timv.com/math/maple/DLL_ErrTest/ It does not matter if I use WRAPPER or not. The error or runtime exeption appears just if number of arguments more than 20. (It can be different types of arguments, not just integers.) I thought may be it is somewere exists an option, that I can increase number of arguments.

There below the college had the same error :( http://2timv.com/math/maple/DLL_ErrTest/ It does not matter if I use WRAPPER or not. The error or runtime exeption appears just if number of arguments more than 20. (It can be different types of arguments, not just integers.) I thought may be it is somewere exists an option, that I can increase number of arguments.

Thank you for repeating my example. I have this problem not just with integer arguments, it is look like a general mistake. Doesn't matter which type of arguments I am using, if number of arguments more then 20 I get such error. So, you think there is no way to avoid reducing number of arguments?

Thank you for repeating my example. I have this problem not just with integer arguments, it is look like a general mistake. Doesn't matter which type of arguments I am using, if number of arguments more then 20 I get such error. So, you think there is no way to avoid reducing number of arguments?

If I run that example with WRAPPER it does't work also, it is giving the kernel runtime exeption.

If I run that example with WRAPPER it does't work also, it is giving the kernel runtime exeption.

It is a possible solution of the problem.

But in my case, i did example with integer variables just to show where the problem.
I have much more complecated structure of arguments.

And it is going to be pain if I will try to do instead of two matrixes one and so on.

It is a possible solution of the problem.

But in my case, i did example with integer variables just to show where the problem.
I have much more complecated structure of arguments.

And it is going to be pain if I will try to do instead of two matrixes one and so on.