Hello @Samir Khan 

These are some general issues that I have ran into using Maple Flow 2024, 2025, and 2025.1 on a Windows 11, Intel i7, 32 GB RAM computer.

1. Improvements in stability of the program: Maple Flow frequently freezes and becomes unresponsive. When this happens, I have to force quit of the OpenJDK Platform binary process in Windows.

2. Improvements in options for executing evaluation: 

A. Results dependent on certain types of Code Window programming are not automatically re-calculated in the Maple Flow canvas without manual intervention. A typical example is a procedure that calls another procedure. The first procedure in this two-procedure example that only depends on parameters from the canvas will re-calculate correctly. The second procedure that depends on the result of the first procedure will not re-calculate unless manually forced (re-execute indivual procedure calls in the canvas, close/re-open the worksheet, or open the Code Window and re-save). Recommend the same options that regular Maple has for one-button click of re-calculation of the worksheet or section.

B. As a work-around to the above, I tried to enable the file option for evaluating all dependent containers and execute the worksheet when saving. This did not work and produced some unexpected results. When trying to save the worksheet, the filename tab below the ribbon display still showed the asterisk (*), indicating unsaved changes. When trying to close the worksheet and saving at the close dialog box, it was the same result. It is necessary to indicate "NO" to saving changes in order to close the worksheet. When trying to re-open the worksheet from recent files, this does not work. You have to open the worksheet from the "Browse" menu. Curiously, after all of this, when re-openend, the previous changes were in fact saved. When I reset the file option back to "do not execute when saving", these behavior anomalies did not happen.

3. Table of contents behavior
A. The table of contents generation frequently does not put the headings in the correct order that they occur in the canvas, observing left-to-right and top-to-bottom evaluation order. After regeneration of the table of contents with no change to the order of headings in the worksheet, the table of contents will often display a different order. 

B. The table of contents will frequently and apparently randomly get the page numbers incorrect in two different ways - simply the wrong page number (usually one page off) or when using sections, have page numbering that appears to start on the page that a collapsed section is on, which is not necessarily the page it will be on in the fully expanded worksheet.

4. Other unpredictable behavior
A. Sometimes I can select/highlight a variable with the mouse for copying, and other times this does not work.

B. When editing a worksheet that uses sections, if you delete or cut a container, the cursor navigates to the end of the worksheet. This is one of the most inconvenient quirks in the behavior of the software.

C. When the print extents option is enabled, it persists when the file is closed and re-opened as long as the Maple Flow program is not closed. If Maple Flow is re-started, the print extents option has to be re-enabled. It would be nice if this setting was saved with the worksheet so that Maple Flow starts with the last configuration without having to re-enable.

D. The text wrapping in a text container does not completely work. This tends to be a problem for the first sentence in a multi-line text container. I have to manually fix this with a forced "return" at the point where the text should automatically wrap.

5. I frequently have to enter numbers in percent. It appears that the only way to do this is to enter a number such as 0.0050, execute, and then change the number format in the context menu to %. This also presents another problem in that the context menu conversion does not use a leading zero and returns .50%. So, if a leading zero is necessary, then a custom number format 0.00% is required. This is a lot of extra work to get 0.50% to simply be entered and displayed as 0.50%. I would like to directly enter the number with a defined % unit that has a leading zero.

6. Phasors do not consistently correctly convert the angle from radians to degrees. Generally, it works with any numeric format. However, if the phasor has a square or n root in the definition, the angle conversion will not work for any defined numeric format. The result will be in degrees, but it will numerically be a radian angle. If the numeric format is changed to "None", the angle in degrees displays the correct numeric value.

I am really rooting for the success of Maple Flow and and hope these issues can be resolved. 

Hello, yes, I see the point FDS 205 is making. I don't see it either.

If it helps, the bookmark to the MaplePrimes, Maple Flow-specific questions and answers still appears to work:

https://www.mapleprimes.com/products/Maple%20Flow

I agree it would be beneficial to have the link restored on the MaplePrimes product list.

@charlie_fcl 

Both responses from @nm worked for me with some minor adjustment in Maple Flow.

I think the only things you need to change in your initial complexplot statement are:

1. reference the imaginary unit as 1i, not i

2. as @nm showed, call the plots package first before using the complexplot command

In Maple Flow, this is the output of your initital statement, with the above modifications (link to worksheet is at the bottom):

For you other question, evalc works and just use 1i instead of i for the imaginary unit.

See the attached Flow worksheet.

Complexplot.flow

I have recently made the switch. I have been a Mathcad user since 1996 and had been looking to transition to "something else" for a long time. I have had good experience with Maple Flow and am happy with the transition. The biggest advantage is that Maple Flow is modern software for one thing - I purchased my last copy of Mathcad 14 in 2009 and have used that since. This leads to a larger user community and just more avenues to share and get help than are available with legacy Mathcad versions. There are lots more formatting features for creating the kind of professional looking documents that you can find examples of in the Maple Flow application gallery. Another advantage is that the Maple programming language is available and from what I can tell so far, substantially works in Maple Flow for anything I have tried to do. I can already see possibilities for integrating workflow with other software tools that I use that either weren't possible with Mathcad or if they were, I never figured out how to do it. Finally, and probably most important, the Maple technical support is very good.

There really are no disadvantages. There is a learning curve, as there is with any software, especially with the syntax. Sometimes the difference between Maple and Maple Flow syntax can add a twist when the help files and other technical support documents available are written for Maple and you are trying to execute them in Maple Flow. But, those aren't really problems - just things that have to be learned.

The best way to learn is just to practice - try to convert an existing Mathcad document to Maple Flow and get up to speed in a methodical way like this.  Get the basic data entry down, then tackle units and creating any custom units that you might use. If you used the programming toolbar in Mathcad, then try to duplicate any programming structures you had in the Maple Flow code editor as that is a bit of a different approach. Then work on the plotting and format your document styles however you want. Those would be my suggestions. And by the way, I would give yourself plenty of time. It is going to be tough if you have to construct a complicated document to match an existing Mathcad worksheet if you are under pressure for a deliverable.

Good luck

@acer 

Thanks for the suggestion. I see from your example how to do this in Maple, but I don't see that this approach works in Maple Flow, which is what I am trying to do. I read in the Maple Flow manual that the typesetting package is not supported.

I am just trying to make sure that there was not some capability in Maple Flow that I was missing as it seems strange that the program does not automatically proportion the fonts in order to avoid the symbol overlap. I can live with typing conjugate() or just using an inline fraction \/ for the case when the conjugate is in the denominator and the bar symbol is desired.

Thanks for the suggestions. op(5,eval(timing)) works for what I am trying to do. I don't get any return values for print statements, but I don't think that is really a problem given that the above works. I just wanted to make sure that I was not missing something with Describe syntax in Maple Flow.

Appreciate the help.