topic Re: Mathcad Prime Issue in Mathcad

Mathcad Prime Issue

MikeArmstrong — Thu, 03 May 2018 16:09:40 GMT

I have just brought a user defined function 'vec' into Prime which takes a single argument and converts to a vector i.e. a range variable. However, I am having an issue typing a range inside pre-definedbrackets.In Prime this does not seem achievable.I must be missing something here!!!

Re: Mathcad Prime Issue

ValeryOchkov — Thu, 19 Jun 2014 06:56:19 GMT

And the second in Prime:

Re: Mathcad Prime Issue

MikeArmstrong — Thu, 19 Jun 2014 06:58:35 GMT

Returning vector a individual nested elements??.

Re: Mathcad Prime Issue

Werner_E — Thu, 19 Jun 2014 10:34:57 GMT

This sure is kind of a sever bug in Prime which you should report!

Re: Mathcad Prime Issue

MikeArmstrong — Thu, 19 Jun 2014 10:54:00 GMT

I will. Valery shown a range can be defined and then passed to the function, but again, this is only a workaround.

Re: Mathcad Prime Issue

MikeArmstrong — Thu, 19 Jun 2014 10:59:56 GMT

Does anyone know the method of reporting bugs?

Re: Mathcad Prime Issue

Werner_E — Thu, 19 Jun 2014 11:09:59 GMT

There is more than just 1 issue!

Not being able to enter a range inside a pair of function arguments parentheses is just one and the minor one I guess. I also quite often happens that Prime will refuse to paste a copied expression (like a cpmplicated function name) at some place, while it will at least allow to retype it there - thats quite annoying and gives the impression of a rather ill-conceived program.

The more severe bug is the different behaviour whether an expression is evaluated on its own or if it is assigned a variable. This is truly very bad! Valery shows this in his second post but it can be also duplicated with the routine in his first file:

Re: Mathcad Prime Issue

MikeArmstrong — Thu, 19 Jun 2014 11:13:32 GMT

That is very poor behavior .

I would be keen to hear PTC's take on this. Why are the elements being nested when in line evaluation is executed.

Re: Mathcad Prime Issue

Werner_E — Thu, 19 Jun 2014 11:17:30 GMT

Mike Armstrong wrote:
That is very poor behavior .
I would be keen to hear PTC's take on this. Why are the elements being nested when in line evaluation is executed.

We don't even know if the displayed structures are valid vectors or something else (ranges,...) as in Prime they are displayed the very same way. I guess that vec(r)[0,0 shown at the lower left in my screenshot isn't a vector anyway. Try to access its first element vec(r)[0,0[0 and you get an error.

Re: Mathcad Prime Issue

Werner_E — Thu, 19 Jun 2014 11:20:45 GMT

Mike Armstrong wrote:
Does anyone know the method of reporting bugs?

You will have to pay (maintanance) for the privilege to do so - crazy enough and tells a lot about PTC's view.

Only way I know of is to use the case logger from the PTC eSupport portal

https://www.ptc.com/apps/case_logger_viewer/auth/ssl/log

Re: Mathcad Prime Issue

MikeArmstrong — Thu, 19 Jun 2014 11:23:02 GMT

We get the same issues in M15.

Re: Mathcad Prime Issue

Werner_E — Thu, 19 Jun 2014 11:44:22 GMT

Wow, thats funny, indeed!

Re: Mathcad Prime Issue

MikeArmstrong — Thu, 19 Jun 2014 11:48:33 GMT

Werner Exinger wrote:
Wow, thats funny, indeed!

Funny or annoying?

I have tried modfying the vec function to include a IsNested trap function but it is not classed as a nested vector so it does not work

Re: Mathcad Prime Issue

MikeArmstrong — Thu, 19 Jun 2014 11:49:41 GMT

Werner Exinger wrote:
Mike Armstrong wrote:
Does anyone know the method of reporting bugs?
You will have to pay (maintanance) for the privilege to do so - crazy enough and tells a lot about PTC's view.

Well my company no longer has maintenance - I will have to wait until the next beta testing and try and report it then.

Re: Mathcad Prime Issue

Werner_E — Thu, 19 Jun 2014 11:57:08 GMT

Funny or annoying?

Awfully bad, indeed!

Ranges can lead to quite confusing effects.

Wish we could get rid of them and use just vectors (as in SMath studio).

Re: Mathcad Prime Issue

MikeArmstrong — Thu, 19 Jun 2014 12:06:04 GMT

Werner Exinger wrote:
Funny or annoying?
Awfully bad, indeed!
Ranges can lead to quite confusing effects.
Wish we could get rid of them and use just vectors (as in SMath studio).

I secondly this. Definately something I will be recommending in the next beta testing.

Re: Mathcad Prime Issue

Werner_E — Thu, 19 Jun 2014 17:49:34 GMT

There are indeed a couple of things to consider if we want to do without ranges and backward compatibility would be a major issue (unless they treat program development still that sloppily as they have done so far).

Re: Mathcad Prime Issue

MikeArmstrong — Thu, 19 Jun 2014 21:56:20 GMT

Werner Exinger wrote:
There are indeed a couple of things to consider if we want to do without ranges and backward compatibility would be a major issue (unless they treat program development still that sloppily as they have done so far).

Backward compatibility does not seem to high on PTC's agenda so why not make the changes going forward.

Re: Mathcad Prime Issue

Werner_E — Thu, 19 Jun 2014 22:52:37 GMT

Backward compatibility does not seem to high on PTC's agenda so why not make the changes going forward.

From what I have seen so far - going forward does not seem to be that high an PTC's agenda as well.

Re: Mathcad Prime Issue

RichardJ — Thu, 19 Jun 2014 23:34:38 GMT

I think the agenda is to go backward with a lack of forward compatibility

BTW, this topic of inconsistent handling of range variables and range values when passed as an argument to a function was discussed a long time ago. I can't find the old thread though.