@vv I agree that an `angle` option on `textplot` would be useful.

But I think that it would need to be dynamically constrained to the aspect ratio of the currently displayed values on the axes.

If it were only a fixed angle in terms of the screen then I don't think that it would be useful for nearly as many plotting tasks.

ps. Someone else showed the OP a link to my old posting about STL import and plotting of 3D letters.

@vv The OP has Maple 7, and plotting images on surfaces is functionality that came many major versions later. 

@rallezet I suspect that what you want can either be done via iteration and rtable_scanblock or possibly ImageTools:-Convolution (plus a few scans or masks, etc).

But your example is too scanty in details to proceed properly without going down the wrong road. Please provide a larger example that contains not just the highest and lowest values but also the boundary values and also some in between. Also useful would be a description of what you want to see in the 1st, 2nd frame, etc, if not the explicit first few frame's Matrices.

@das1404 A help page that almost every Maple user should read is for the topic plot,options . (You should read the one in your Maple 7, of course, and not the modern one in that Online Help link.)

In this case, it is the option style that is most relevent.

The style patchnogrid (now aka polygon) is not related to Maple's patchlevel. You are correct, it does mean that the polygon is filled (shaded) and its outline is not shown differently.

@das1404 Does this work in your Maple 7?

restart;

with(plottools):

makeA:=proc()
  local opts;
  opts:=style=patchnogrid,color=gray;
  plots[display](
    plots[polygonplot]([[0,0],[1,0],[4,8],[3,8]],opts),
    plots[polygonplot]([[3,8],[4,8],[7,0],[6,0]],opts),
    plots[polygonplot]([[2,4],[5,4],[5,3],[2,3]],opts),
  scaling=constrained);
end proc:

P1:=makeA():

P1;

plottools[rotate](P1, 2*Pi/3);

@das1404 You can delete the "uses" line inside the proc, and change each polygon to plots[polygon] instead.

But do keep using procedures, to organize your jobs. Write a procedure to create the plot of the capital "D".

Like all your previous queries, I converted this from a Post to a Question.

Are you saying that you want the different branches of the piecewise to be visually distinct? If so, then how do you want them to differ visually? With different colors? Or different styles for the lines?

Do you also want the different contour values to be distinct from each other, say by some graded shading?

If you want the piecewise branches to have distinct colors, and also the contour values to have graded shading, then perhaps you could suggest what colors and gradients you'd like.

Use the green up-arrow in the editor here to upload your actual worksheet or document.

It's unclear exactly what commands you've executed, otherwise.

@assma You should be able to use the ExportMatrix command with that numeric Matrix.

@Preben Alsholm That is weird. It seems to have changed between Maple 12.02 and Maple 13.00. (Report submitted)

@Joe Riel Hi Joe. I didn't mean that it's tough in principal. I meant that it's awkward and tough for most users to do by hand.

After all, calling if...then with is in the conditional is clearly tough for many users to figure out, since it is a faq.

This thread strikes me as being in the classic theme of technical correctness versus practicality. A didactic view is to restrict attempts to only classes of problem for which results may be guaranteed, etc. But that approach would never have given us the awesome usefulness of the simplify command.

Is the pattern that `max` and `sort` are still using evalb for relation testing? Maybe it's time to consider promoting `is` to a new job.

For `sort` you can supply your own comparator (as I know you're aware) but there's still an argument to made for having it be more automatic. For `max` it's tougher to do it efficiently.

The generated 3D globe plot consists of POLYGONS with many (approx. 30-40k) elements, CURVES for the borders, and a MESH for the sphere/ocean. Those main substructires can all be manipulated separately, even obtaining a few customizations not easy (or possible) directly from the original command.

globe_fun.zip

@Preben Alsholm 

I'm not sure I understand why evalf/Int isn't succeeding (and quickly) by splitting the integral at x=1 the point of discontinuity in the given range x=0..5.

restart;
g:=sqrt(1/(1-x^2)):
CodeTools:-Usage(evalf(int(g, x = 0 .. 5)));
memory used=52.37MiB, alloc change=34.00MiB, cpu time=502.00ms, real time=502.00ms, gc time=39.53ms
                  1.570796327 + 2.292431670 I
restart;
g:=sqrt(1/(1-x^2)):
CodeTools:-Usage(evalf(IntegrationTools:-Split(Int(g,x=0..5),
                          select(x->x>=0 and x<=5,[op(discont(g,x))]))));
memory used=20.81MiB, alloc change=67.01MiB, cpu time=216.00ms, real time=216.00ms, gc time=15.67ms
                  1.570796327 + 2.292431670 I
restart;
g:=sqrt(1/(1-x^2)):
CodeTools:-Usage(evalf(Int(Re(g), x = 0 .. 5))
                 +evalf(Int(Im(g), x = 0 .. 5))*I);
memory used=6.15MiB, alloc change=33.00MiB, cpu time=67.00ms, real time=66.00ms, gc time=5.67ms
                  1.570796327 + 2.292431670 I

Everything has the same sign, approaching the discontinuity at x=1 from both sides.

plot([Re,Im](g),x=0..5,view=0..5,thickness=4,filled,color=[green,red]);