V1.5.19 Crashes

[Wirmike]

When duplicating an existing transaction MMEX crashes.

The issue seems to arise after I have exited the Numbers field.

Below is a real (non-sensitive) example, followed by the small error-window:


Example>
—————-

“APPLEPAY: 15h59; (TILL: 14h18!;)”

Error-Window>
————————-
“Invalid Value
1: ‘end’ expected near ‘(‘“

As a result I will be reverting to v1.5.18 - pro tempore.

Hope that this is useful.

My OS is Mac OS 10.13.6.

Regards.

Ps. Thankyou for fixing the Decimal 999.99 limit issue on the Custom Fields.

[MartinArmstrong]

Does not crash on Windows.

Because of issue https://github.com/moneymanagerex/money ... ssues/4951, the letters get stripped as shown below.

As entered on the left. As saved on the right.

Number field.png (32.69 KiB) Viewed 1546 times

[MartinArmstrong]

@Wirmike
Can you confirm that MMEX does actually crash, as per your thread title?

Or do you just get the pop-up error message: Invalid Value 1: ‘end’ expected near ‘(‘ when entering/editing a transaction Number field.

[Wirmike]

Yes. MMEX seems to freeze and I need to Quit to continue and re-launch. MacOS generates a error report to send to Apple.

Puzzling.

Ps.

I tried to Duplicate an EXISTING transaction, make an amendment, w/out touching the Numbers field. The Duplicate was successfully saved w/out a crash.
I then tried to edit the Numbers field of the Duplicate… the programme then crashed and froze. After quitting and re-launch I looked at the Original and Duplicate transactions’ Number fields.

Original and Successful Duplicate>
————————————————————
“APPLEPAY:13h45; (TILL: 13h47);”

Now Error-Modified Duplicate>
——————————————————
“1345(13)”

The error has modified the original numbers entry as a ‘sub-set’ type extract of the original!

How the WIndows version would behave with the original Numbers entry as a starting point, I don’t know.

Regards

[MartinArmstrong]

This bug in 1.5.19 is understood and will be fixed for 1.5.20.

In the meantime, you could reinstall 1.5.18 and continue as before until 1.5.20 is available.

[Wirmike]

I have just downloaded the WIN(64) version to my wife’s WIN11 HP.
Running a copy of my main .MMB file from A USB on the HP I can confirm that even though I modify the Numbers field, MMEX does NOT crash or freeze. However, the Numbers field is contracted in a similar way to that on the Mac.
Out of interest I had a look at the Custom Field in which I have entered a value >999.99 - that is recorded correctly.
I checked out the currency change of “Scale” to “Decimal Places”. This remains as “Scale” in both the WIN11(64) and Mac versions - I have only checked the currency option via the ribbon at the top of the screen.
But, when exiting this check (from the currency parameters) on the Mac I had another Crash/Freeze this time w/- the little error-window referring to “near ‘;’ ”.

It seems that the code is being super vigilant at interpreting semi-colons as a statement terminator in the wrong places. Maybe?

Curiouser!

I have just seen the post from MartinArmstrong and will do as suggested. But the rest on my post may be of interest.
Regards.

Ps. Thanks to MA for being quick on the fix - I await v1.5.20.

[MartinArmstrong]

All this is known. Thanks @Wirmike

BTW, it's not me making the fixes. @whall3y is doing that.

[Wirmike]

Following the last post from @MartinArmstrong, a thanks to you, @whall3y!

Roll on v1.5.20!

[whall3y]

Following the last post from @MartinArmstrong, a thanks to you, @whall3y!

Of course it was me that introduced the bug trying to fix something else, so no thanks due

[Wirmike]

I have now downloaded v.1.5.20.

I am pleased to say that I can now save a DECIMAL Custom Field =>999.99 successfully… and NO crashes!

Thanks to @whall3y.

In the meantime I have been having a problem using the Transaction Filter, with Custom Fields selections, that seems to persist into v.1.5.20. But that will be the topic of a separate post.

Thanks again.