@Shaggy 

Try re-sizing each text container and you should be able to reproduce the problem. Some lines of text will automatically wrap and others will not.

Ok, I have a reproducible set of steps for this now. Again, I'll try to get this fixed for the November release.

Thank you for following up on this...this is valuable.

@Shaggy 

You will see the variable Op__time1 in the section "Timing Data" refresh immediate. It is only dependent on one procedure call. The remaining variables that begin with Assess do not refresh without manual intervention. This timer operates on two procedure calls.

OK, yes, I can reproduce this - thank you for bringing this to my attention. I'll attempt to get this fixed for the November release.

For the navigation issue, collapse the section header "Timing Data". Then, underneath the section line, type a text container and then select and delete it. This may not do anything. If it didn't work, try typing text above the section line, deleting it and then typing text again below the section line. This should cause the navigation jump.

I still can't reproduce this. Could you go to Help > About Maple Flow, and tell me your Build ID?

@Shaggy Thank you for the detailed feedback. Keep it coming!

I want to get to the bottom of all the issues you've described. .

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

Is this behaviour across all worksheets, or to a specific worksheet? Could you describe the content of worksheets where this happens? Perhaps even post one?

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.

I've attempted to reproduce this behaviour based upon the description above but have not been able to. Can you provide an example please?

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.

On output:

I've logged the bug with the disappearing leading zero if you format a number as a percent. We'll get this fixed (if not for the November release, then the release after that

On input:

We've had many requests for % to mean 0.01 in Flow. So you could just type 50% to evaluate to 0.5. We have to think carefully about this because % already has a meaning in the Maple programming language (FWIW I'd be in favour of %=0.01 in Flow)

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

This is a known bug. 

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.

I know this bug was present in older versions,but I don't see it in 2025. Do you? If so, can you please describe the steps to reproduce this behaviour

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.

Print Extents will be a global setting for Flow 2025.2 (ETA November 2025)

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.

If I 

• click on a blank part of a worksheet
• press Space to create an empty text box (by default non fixed-width)
• type the first word of my sentence
• resize the text box so it becomes a fixed-width text container
• continue typing the rest of my sentence.

...the text wraps as expected.

If I may ask, could you describe the steps you take to produce this buggy text wrapping behaviour?

@FDS Yes of course. One of my colleagues will be in touch

@manasp One of my colleagues will reach out and give you a download link for the Migration Assistant

@MichalKvasnicka Apologies for the out-of-date online help. We're working on updating the online help to reflect the latest Maple version.

@MichalKvasnicka Sorry, we had some IT issues that we are still working through.

This isn't a bug.

Maple Flow offers "units balancing" to make a result dimensionsally consistent. If a result is in J (energy), you can ask Maple Flow to rescale it to any consistent compound unit that contains m. Flow does some dimensional analysis, and automatically includes a unit correction factor of N (so the complete unit is N*m)

Maple doesn't offer automatic units balancing. You have to specifically ask Maple to rescale J to N*m.

Claus, could you provide more detail please? I can use both area and speed units in 2024.2 (entered via the Units palette, and manually via the units placeholder)

Claus, we've just updated Flow 2024.2.

In Flow, could you go to "Tools>Check for Updates" and install the latest version. I anticipate this will fix the issues you describe above.

@C_R Customer Service can still provide the previous version. But we're hoping to release an update to fix these bugs sooner rather than later.

Hi Claus

We can reproduce this bug if numeric formating is applied to an expression sequence or list. Please bear with us as we investigate a possible fix.

While we investigate, can you remove any numeric formating from your results (either local or global)? Does that work for you?

Samir

@Claus Wehrmann 118 

ifactors(3032) works fine for me with no crashing

Could you send an email to tech support (https://www.maplesoft.com/contact/webforms/support.aspx) with your build number (from the Help>About menu) and OS describing these issues?

Could you supply a specific example?

As far as I see, fsolve in Maple Flow 2024.2 returns all the roots of a polynomial:

@WhiteNoise We've thought about bringing phasors into Maple as well, but there are no firm plans. But the more people that want this, the more likely it is to happen.