I showed a similar thing here, using the events functionality of numeric dsolve.

(I also showed it there using Optimization:-Minimize.)

Every call to DocumentTools:-InsertContent entirely replaces any content in the sole Task Region that an Execution Group can have.

In other words, each time through your loop the InsertContent call will wipe out whatever was inserted the previous call.

You cannot work around this with the kind of looped call to InsertContent call that you have.

You can only work around it by inserting xml content which itself contains all the augmented content.

Eg, hyperlink_do-loop_1.mw

So you can use a seq call within the construction. But you cannot succeed doing any looped call to InsertContent.

You have other choices, about what to enclose within such a seq call. It needn't be of the form seq(Group(Input(...)),...) but instead could be different hyperlinks in a sequence of Cells in a Row, or a particular Cell in each of a sequence of Rows in a Table, or a particular Cell in a sequence of subTables within whatever, etc.

My personal preference for such tasks is to try and target any actions by expand, simplify, combine, etc, to only those which are necessary, in as much as that might be possible.

Restricting use of simplify can be more important, since it can turn ln,exp to arctrig,trig form.

This version also separates factors which do not contain any of the names, or those which are not separable. It handles 1, 2, or more arbitrary names.

Download splitprod.mw

No, that is not offered through Maple for that computation (ie. grinding it out via `isprime`, as opposed to lookup via NumberTheory:-IsMersenne).

Let me know if you'd really rather have the phi details inside the plot (which could be done using a fancy textplot).

Legend_1.mw

Using the menubar, select to View -> Show/Hide Contents...  and in the popup dialogue that appears toggle off Execution Group Boundaries.

Note this is a property of the Worksheet itself, rather than a global setting. Which means when the sheet is saved it retains the property when re-opened (by you or someone else). It also won't affect other newly opened sheets. 

Download solve_r.mw

For AudioTools:-Preview to recognize a float[8] Array as an audio thing it has to have certain attributes.

In Maple 2017 the Statistics:-MovingAverage operation does not return an Array with the attributes of the original its input Array. But in Maple 12.02 that command did do that.

I don't really understand how a computation like that done by Statistics:-MovingAverage could sensibly just copy over values for audio qualities like sampling rate. Simply giving the same audio attributes to the returned result doesn't make much sense to me. Perhaps even more importantly, what about the case that someone has used atttributes to mean something else entirely, for which blind copying over of attributes bu MovingAverage might make no sense at all.

Perhaps audio things could be implemented as objects. Then their data could be extracted on demand, but it'd be more obvious that manipulations of such data would then just be Arrays of revised data, and not new audio objects per se.

You could put the attributes of a onto d, or you could apply the AudioTools:-Create command to d to set its audio attributes. You may need to think about what values to use.

audio_prev.mw

Computations are performed on the local computer than is running Maple.

(There are some very uncommon and specials ways to communicate with other machines/servers, but it has to be done purposefully and many people would not even know how. So, to a practical extent: all computations executed in your standard Maple program will be computed locally.)

As for indications of progess, well that depends very much on what kind of computation. And you've told us nothing about the particulars.

Is it a computation done by a procedure (not just a document) written by you? If so then you can inject periodic messaging code into it, in several different ways.

For quite a few Maple stock commands you can also adjust the infolevel setting, to get some progress notes. Note that the extent of such detail varies quite a bit, from command to command.

There are also ways to get Maple to plaster your screen with almost all that its doing at the interpreted Library code level. But this is usually so overwhelming that its not helpful.

This can be controlled manually using the the Typesetting:-RuleAssistant popup, or programmatically using the Typesetting:-Settings command.

This setting is not saved as part of the Worksheet/Document, nor can it saved as a global preference.

But you can hide preliminary calls to commands Typesetting:-Settings in the Startup Code region of the sheet, and so get such settings to be specific to the particular sheet.

Download primediffparsing.mw

If you change that to Shutdown("0") then the return value wil be the string "0" upon Cancel (and, as you've implemented the other button, a list containing the selected filename string otherwise).

Assign the return value directly to say f1, and leave indexing into it until after you've tested whether it is "0".

You can just check evalb(f1="0") and then return/break/next/stop/end/etc as you wish. If it isn't then you can index into it like f1[1], etc, to get at the filename.

You can use subsindets and type anyfunc or type specfunc to find and act directly upon (ie. freeze) all those subexpressions which you don't want to be combined.

For example, excluding any function of alpha or beta,

thaw(combine(subsindets( expr, anyfunc(identical(alpha,beta)), freeze)));

Or, restricting it to just a few particular functions such as any combination of sin or cos of alpha or beta,

thaw(combine(subsindets( expr, specfunc(identical(alpha,beta),{sin,cos}), freeze)));

For handling an explicit (and small, say) list of items to exclude the choice is a matter of personal preference, I'd say. I find that I usually reach for subsindets so that I have less editing to do if I want to switch from a fixed list to more encompassing type. For example, to work on expression expr,

L:=[cos(beta),sin(alpha)]:
thaw(combine(subs(((x->x)=freeze)~(L),expr)));
thaw(combine(eval(expr,((x->x)=freeze)~(L))));
thaw(combine(eval(expr,(x->x=freeze(x))~(L))));
thaw(combine(subsindets(expr,identical(op(L)),freeze)));

I pointed out a new bug in the parsing of 2D Input, new to Maple 2017, on Sept 7th, 2017 in another thread on Mapleprimes.

There is a new problem in that infix arithmetic operations are being parsed to prefix function calls. For your example done in 2D Input Maple compute the float reciprocal of the denominator first, and then multiplies the numerator by that preliminary result.

Of course, compared to using proper float division, that new behavior can violate the expected behavior of attaining no more then 0.6 ulps error for the atomic floating-point arithmetic operation.

I recall that the rules for when this happened for 2D Input infix arithmetic operations, or not, were all over the map.

I submitted at least two bug reports related to it, at that time. (The bug report submitted approximately Sept 7th did not make it to a fix for the 2017.3 point release of Oct 3rd.)

I'll note that your Question's input appears to be in 1D Notation input. But you also indicated that it made a difference whether you were in a Document of Worksheet. It may be that the disctinction occurs, say, between a Document Block and a plain Execution Group. It would help if you uploaded your document as an attachment rather than just inlining images input in your Comments.

If you are passing a list of expressions to plot then you can also pass a list for the legend option. Eg,

exprs:=[sin(x), cos(x), sqrt(x)*sin(x)];

plot(exprs, x=0..6, legend=exprs);

Download sys_fsolve.mw

[edit] Having obtained a solution, there will be another with values for y and z interchanged (due to symmetry).

sys:={x^2 + y^2 + z^2 = 4, x + y + z = 0, x*sin(y*z) = -1}:

evalb( eval(sys, [y=z,z=y]) = sys );

                    true

So swapping values for y and z is another way to get a second solution.