font problem

[Angela M]

Hello nitad54448,

I wanted to add a comment about the difficulty of this CAR.  All known reports have happened in LabVIEW 8.6.x.  We have never been able to reproduce the issue from scratch, so we are not currently sure of the cause.  That being said, if you are able to get us a copy of your code, we may be able to help you return it to a readable state.  (I believe you may have already contacted us in private to help with this, but if not, please do so.)

Not sure if it was mentioned earlier in this thread, but we have had no reports of this happening in LabVIEW 2009, and since there was some rearchitecting of this code, we do not anticipate the issue recurring.

We definitely agree that this is undesireable behavior, and if we can identify a way to resolve the problem, we will let you know.

Regards,

Angela M

Staff Product Support Engineer

[nitad54448]

---

Smootastic wrote:

Hi nitad54448 

Unfortunately, this issue has been reported in Corrective Action Request (179683) and is currently under investigation by R&D.  For now, a potential workaround is to convert the controls/indicators to constants and revert them back.  Additionally, this appears to be an issue when using a VI that has been built into an executable.

I'm sorry for the inconvenience. 

---

Hello

Indeed this converting of controls into constants and back might be a solution and I already started to do so. However, since this is very large vi with several dozens of controls on a eigth pages tab, I was not attempting the changes into constants .Moreover, most of the controls have limited values for entry (for instance for a current source, the user is not allowed to type a value outside of a range say 0.0001 to 0.10...); by changing to constant and coming back these limits are lost...

So, I am hoping to find a better solution (I removed most of the fonts from the system : nothing changed).

I will probably need to upgrade* and I am not happy about that ! 

N

* Can you open the example VI in this thread with LV9 and see if you can change the fonts to something readable ?

Message Edited by nitad54448 on 02-19-2010 02:43 AM

[RavensFan]

Perhaps it would be worthwhile to turn to scripting.

Write a small VI that takes the needed information out of the control such as data entry limits.  Programmatically change it to a constant.  Programmatically change it back to a control.  (Maybe put a 1 second pause in between so you can see the changes.)  Then restore the collected information from the first step back into the control.

With this, it can be a one click process to fix them.

(You could theoretically loop this and have it operate on multiple controls, but I think a one click process to fix each control would speed things up tremendously and give you some control (no pun intended) on which controls to work on.)

Message Edited by Ravens Fan on 02-19-2010 11:56 AM

[nitad54448]

---

Angela M wrote:

Hello nitad54448,

I wanted to add a comment about the difficulty of this CAR.  All known reports have happened in LabVIEW 8.6.x.  We have never been able to reproduce the issue from scratch, so we are not currently sure of the cause.  That being said, if you are able to get us a copy of your code, we may be able to help you return it to a readable state.  (I believe you may have already contacted us in private to help with this, but if not, please do so.)

Not sure if it was mentioned earlier in this thread, but we have had no reports of this happening in LabVIEW 2009, and since there was some rearchitecting of this code, we do not anticipate the issue recurring.

We definitely agree that this is undesireable behavior, and if we can identify a way to resolve the problem, we will let you know.

Regards,

Angela M

Staff Product Support Engineer

---

Hi

Thanks for the message. I can send you the vi if you can convert it back but I can not post it here.

The problem is that in about 30% of the compilations of this particular vi I get the "square bug" so it might bbe destroyed again sometime later. Do you think that the square fonts can be corrected in LV2009 ? 

On another note, if you want, I can compile for you some test programs if you send me in order to see if this bug is occuring, maybe you can dig out where the problem is.

regards.

N

[nitad54448]

hi ravens

thanks for the tip but I think it is too complicated: also, when converting a constant back to a command, its position and all characteristics are lost, so I need it to do manually... I am hoping thatopening in another version can modify the fonts then saving in 8.6could also be a solution. I posted a problem vi in this thread maybe someone can give  it a try,

N

[RavensFan]

---

nitad54448 wrote:

hi ravens

thanks for the tip but I think it is too complicated: also, when converting a constant back to a command, its position and all characteristics are lost, so I need it to do manually... I am hoping thatopening in another version can modify the fonts then saving in 8.6could also be a solution. I posted a problem vi in this thread maybe someone can give  it a try,

N

---

You must not have completely read what I had written.  If you aren't familiar with scripting and haven't used it, then I can understand wanting to avoid it.  But if I was faced with having to modify hundreds of controls and it would take me hours, I'd invest an hour in writing a script to do that for me much more quickly.

You won't lose the characteristics of your controls because what you'll do is read those characteristics in your script before you make any modifications.

1.  Read all the characteristics from the control that you will want to restore:  position, data entry limits, .....

2.  Convert the control to a constant.

3.  Convert the constant back to a control.

4.  Write the characteristics back to the control.

If I get a chance later today, I'll see if I can work up a script that will act on your corrupted VI.  But, I've got some other things I need to do today first.

[nitad54448]

---

You must not have completely read what I had written.  If you aren't familiar with scripting and haven't used it, then I can understand wanting to avoid it.  But if I was faced with having to modify hundreds of controls and it would take me hours, I'd invest an hour in writing a script to do that for me much more quickly.

You won't lose the characteristics of your controls because what you'll do is read those characteristics in your script before you make any modifications.

1.  Read all the characteristics from the control that you will want to restore:  position, data entry limits, .....

2.  Convert the control to a constant.

3.  Convert the constant back to a control.

4.  Write the characteristics back to the control.

If I get a chance later today, I'll see if I can work up a script that will act on your corrupted VI.  But, I've got some other things I need to do today first.

---

Hi

sorry, I am not familiar with scripts... more, I want to find the source of the problem because this is appearing quite often !

[RavensFan]

I can't help with the source of your problem.  NI will have to figure that one out.

But I did work up a script in LV8.6.

1. Copy this VI to your desktop.
2. Make a copy of one of your problem VI's.  (Don't want to screw one up in case I did something wrong.)
3. Run the Script VI.
4. Open the block diagram of your problem VI.
5. Select one or more constants, control terminals, or indicator terminals.
6. Click the button on the running script VI.
7. It will go through and change controls to constants, back to controls.  Or constants to controls and back to constants.  It will maintain the position on the block diagram.  For controls and indicators, it will maintain their position on the front panel.

I did not do anything for data entry limits or any other properties.  Those other properties would need to be added in the same way that the position is handled.  It might even require casting the control references to a more specific class to be able to access those properties in a property node.  But at least this will give you an idea of the power of scripting.

[nitad54448]

hi ravens,

i will look at this tomorrow at work !

thanks a lot !

N

[nitad54448]

Hi

the scritpt works fine ! I can see now the text ! Thanks a lot !

Regards

N.