01-15-2012 08:38 AM
Solved! Go to Solution.
01-15-2012 09:28 AM
01-16-2012 08:45 AM
Hi,
I would say this is normal behaviour. When I set up an example VI and insert a string and make it a Typedef I can't select "scale with pane" either.
I guess the option is simply blocked for Typedefs. It would make sense, too, because when the application runs, the Property would have to be changed for all representatives of the typedef.
Best regards,
01-16-2012 01:22 PM
jak888 wrote:I would say this is normal behaviour. When I set up an example VI and insert a string and make it a Typedef I can't select "scale with pane" either.
I guess the option is simply blocked for Typedefs. It would make sense, too, because when the application runs, the Property would have to be changed for all representatives of the typedef.
Hi Peter,
I would agree if this was for a STRICT typedef. As far as I understood it, the idea of (non-strict) typedefs was that you could actually change how the control would look in each instance. Even if it was a strict typedef, why would anyone want to prevent the developer from making 20 equally sized panes?
Thanks,
zeeed
01-18-2012 03:25 AM
Hi,
after looking into this deeper I found out, that if you first make the indicator scalable with pane and then make it a typedef, that indicator will scale with pane. However, if you copy the typedef, the scale with pane beaviour disappears.
This definitely isn't the behaviour you would expect. That's why I filed a CAR for the Issue that has the Number 333531
If you get the new Version you have to look for the Number in the release notes. If it appears, the issue has been fixed.
Sorry for the inconvenience.
01-18-2012 06:26 AM
Hi,
thanks for confirming. Yes, I noticed the same behavior (scaling to panel first and then converting to a typedef) - another reason to assume that the change in the context menu must be erroneous.
Best,
zeeed