The OP wrote, in a followup comment, "how to draw all the lines P1P2,P2P3,P3P4, etc,  and the incirles of centers C1, C2.."

The OP's earlier code did not define C2, however, so I have made a guess as to that (and to the incircles).

Download jamet_ac2.mw

@JAMET You now seem to be calling plot instead of plots:-pointplot.

Why did you change it?

(You could attach a worksheet containing the code you actually use. That could save effort, all round.)

I am unable to get either of the pair of tubeplots to be rendered in black, using Maple 2022.1 for ubuntu 18.04 LTS, with hardware acceleration turned either on or off in the GUI Options.

Why not simply provide your full requirenents on your other, recent Question on this?

You could zip-compress-archive the file, then upload and attach the .zip file using the green up-arrow in the Mapleprimes editor.

@Carl Love A PlotComponent allows for properties (clickx  clicky) to be queried programatically. Those can be used with a single right-click, or click&drag.

The `Explore` command allows for this by having two (or one) parameters be specified via its `markers` option. Additionally, the corresponding Sliders may be shown, or suppressed. See ?Explore as well as ?examples,Explore .

The above have a notion that the scale of the parameters is the same as the scale of the 2D plot. Naturally, if the interactive plot is 3D then such marker-style interaction (on a 2D plot area) would need to be in a separate plot, by the side say.

I'm away from a computer until this coming Sunday  and then again from Mon-Fri. Apologies not being to show examples by code.

[edit. If I can paste properly...]

The parameter values taken from a 2D plotting area can be used as simply the x,y values of an input point. Or they can be used as a pair of parameters used in some quite different manner of your own devising.

IIRC, here's an Explore app that used markers to grab an x-y point input on-the-fly,

https://www.maplesoft.com/Applications/Detail.aspx?id=153552

And here's an embedded components app that also used clickx,clicky (but not via Explore) to control parameters,

https://www.maplesoft.com/Applications/Detail.aspx?id=153557

As far as a (forcing) programmatic transformation goes, do you care whether it is always valid?

ps. Is this entirely different from all your earlier queries on 2-argument arctan, and if not then why split up the topic?

@Christian Wolinski I believe that the OP is aware that he can write it out, with the body of the inner procedure hard-coded. Ie, more tersely,

f := a -> (b -> a/b);

      f := a -> b -> a/b

f(A)(B);

            A/B

I believe that the OP's issue was in programmatically building f such that the body of the inner operator was constructed from the predefined expression e.

@vv If g changes then the efficient course would be to rebuild dgdx2. (The efficiency alluded to is the cost of repeatedly invoking D for each call to dgdx, not the cost of construction.)

In terms of simplicity but with a similar inefficiency, forming dgdx2 once, prior to defining g, makes it behave like dgdx1, ie. consistent results. (But it's still simpler and more straightforward.) Eg,

dgdx1:=(x,T) -> D[1](g)(x,T);
dgdx2:=  D[1](g);

g := (x, T) -> T*x + x^2:  #just an example
dgdx1(1, 2);
dgdx2(1, 2);

g := (x, T) -> T*x + 7*x^2:
dgdx1(1, 2);
dgdx2(1, 2);

@Saha 

You've accidentally pasted Tom's 1D plaintext code in as 2D Input, without altering it to avoid (incorrect) implicit multiplications.

You've changed the boundary conditions in two different ways (both invalid).

You've changed f(x) in one of the equations.

@vv If g has already been defined then I don't see why you'd want to incur the cost of having dgdx invoke D each time it gets called, instead of simply assigning,

   dgdx := D[1](g);

@FDS What I gave originally was 4x1 Matrix. I've edited it to return a column Vector.

@mehran rajabi You could upload and attach the worksheet in which the plot is not displayed for those commands...

@Carl Love For no reason except that I think this looks nifty.

(edit: one reason is that shading=xyz can convey some depth, which is less clear with a monochromatic curve.)

Done in Maple 2018.2 for Linux.

Download deplot3drev.mw

@dvilla It is possible to programmatically embed a plot with a specified zoom scaling (zoom) factor and adjusted vertical (or horizontal) offset within the inlined plotting window. In other words, to take the burden off of the end-user, and to allow you to enforce the initial aspect.

In the following worksheet the plots get "displayed" (even from scratch) just as shown. I appreciate such programatic vertical trimming of blank white space, if I do not intend to rotate the 3D plot head-over-heels.

prog_zoomtrans.mw

Unfortunately this forum's backend baulks as rendering this worksheet.

Those wrapping commands which force the scaling/offset/etc could easily be made into a reusable procedure, which could also be optionally hidden -- say in the Startup region of the worksheet.

An alternative is to rescale the formula and then force new tickmarks, but it can get complicated to implement robustly as a general mechanism. 

I used Maple 2022.1, and got no disk artefact. But that's a separate issue to getting the zoom, offset, aspect ration, etc, just as you want.