Bug? Dimensions using User Parameters only show "fx:" prefix sometimes...

[robduarte]

Please see the attached screencast. I show two cases: one where a user parameter is the dimension and the other where user parameters are part of an equation. The "fx:" prefix only appears after I make a change to the user parameter. I don't recall this being the case so I wonder if this is a new issue.

http://autode.sk/1OtXKJV

[Anonymous]

Yeah, I recently noticed driven dimension text problems too.  Besides the fx not showing up, a different behavior that is normally the default for me is getting scrambled text:

It looks like it's trying to display the number value twice. 

The quickest way I found to correct it is just double click on the text to bring up the little edit window, then hit enter.  You get to where it just becomes something automatic to quickly do for each driven dimension.

Jesse

[jeff_strater]

yes, that's a bug all right.  I'll report it and we can investigate further.  There have been another couple of reports recently of dimension/equation strange behavior.  Not sure if they are related or not.

Jeff Strater (Fusion development)

[daniel_lyall]

I have had that to moveing the demention fixes it as well.

[robduarte]

Moving the dimension may fix the garbled appearance, but it doesn't fix my original issue. It's been quite a while and it looks like the same issue is still around. Here is an example of the steps to reproduce:

1. sketch a 2 point rectangle with 100 and 100 as the dimensions

2. create user parameters called "width" (100) and "height" (120)

3. replace each dimension with the new user parameters.

When I do this, only one of the dimensions shows the fx (the height dimension). The other still shows 100 (even though double clicking the dimension shows that the user parameter is being used).

[robduarte]

Jeff, this is still a bug in the most recent update (feb 2016). Should I report it somewhere other than the forum or is this on a list somewhere already? Thanks

[jeff_strater]

Thank you for pointing that out @robduarte.  Sadly, you are correct, the issue still seems to exist.  I will follow up, no need to do any more on your side.

Jeff

[ShirleyShi]

Thanks all for the follow up.

This defect has been fixed and will be available on next release.

Thanks,