AnsweredAssumed Answered

SolvedQuestion about ExpandDuringEdit

Question asked by wangyiliu99 on Jun 12, 2013
Latest reply on Jun 21, 2013 by Mike

Like • Show 0 Likes0
Comment • 8

Hi, all,

First of all, my VEEPro version is 7.5

The following is selected in VEE menu
Data>Constant>Real64

Then I got a box. When I input value say 1, then the value would be changing to 1.000000xx
after the text editor is not activated.

For the properties, there is one option "ExpandDuringEdit"
Default value is true, when I change it to false, problem solved.

However, when I select this box,
Edit>Add to Panel

I noticed that when the box is in panel view, it also have those properties, like the "ExpandDuringEdit"
default value is true. So I changed it again to "fault" to avoid the data change.

My question is,
In these cases, does it mean that for certain properties, the value needs to be set twice, both in the detail view and panel view.

Your help is highly appreciated!

Yours,
Yiliu

Edited by: wangyiliu on Jun 14, 2013 4:22 PM

Edited by: wangyiliu on Jun 19, 2013 6:39 PM

No one else has this question

Outcomes

wangyiliu99 Sep 24, 2013 3:15 AM

sorry to bother again,

via searching this forum, I found the answer,

simply not use the
data>constant>real32,
but
data>constant>text

can solve this problem.

But would anyone help me with the case, while data is not input by the Text editor,
but from a *.txt file.
READ TEXT
command formats are quite a lot.

However, how could get 100.2 exactly 100.2, rather than 100.200000xxx

BR,
Yiliu

Actions

Mike @ wangyiliu99 on Jun 13, 2013 4:54 AM

Yes this is a recurring theme - in my view this is a bug in VEE - others will tell you that it is correct because the underlying binary cannot exactly represent these numbers ( not quite true actually ) - but I think that if I enter 8.9 that's what should be printed, displayed etc.

You have found the solution, use text for input and ensure you format numbers for output ( even that fails sometimes due to this 'feature' of VEE.

Not sure if that is helpful, beyond "it's a known problem and you are dealing with it the same as the rest of us".

Actions

wangyiliu99 @ Mike on Sep 24, 2013 3:15 AM

Hi, Mike

thanks a lot.

b.t.w., do you know any function that could
change data format say, string to real?

Actions

wangyiliu99 @ Mike on Sep 24, 2013 3:15 AM

Hi, Mike,

would you please take a look at the snapshot of my VEE window.

We could see that the ExpandDuringEdit is "False",
but still we could see the value shown in yellow has so many digits.

I am really so tired of this.....

Anyone, please help!

Attachments

ExpandDuringEdit.JPG43.1 KB

Actions

wangyiliu99 @ wangyiliu99 on Sep 24, 2013 3:15 AM

after checking carefully about the properties of the Real32,
I found the "NumFormatfor" property and snapshot is attached here.

In this setting, the value displayed in the editor box is okay, however,
when check its value by putting the mouse on the line, it is still with so many digits

Yiliu

Attachments

NumberFormatfor.JPG35.0 KB

Actions

Mike @ wangyiliu99 on Jun 14, 2013 3:22 AM

You cannot format the tooltip or 'line probe' as it's called. I agree it is annoying.

Regards, Mike

Actions

wangyiliu99 @ Mike on Sep 24, 2013 3:15 AM

Hi, Mike,

today I contacted agilent support Japan and got the problem solved.

the method used is: (sample is shown for the case only one digit after the period)
(1) 10 times the number
(2) round that number to the nearest integer
(3) divide that number by 10

to get the say 100.1 exactly.

Attached is the reference program.
Enjoy

Attachments

SampleRound.vee5.0 KB

Actions

Mike @ wangyiliu99 on Jun 21, 2013 8:44 AM

Unfortunately you've been duped! The functions you have used have converted the number to a Real64 which seem to represent your number in the way you'd like to see it ( and the way every other language does it ). I have attached a simpler example which does what you stated but if you hover over the line you'll see it is not the number I entered.

I'm afraid that, like me, you'll just have to live with it and make work-arounds whenever you want to display or have a user enter a value.

What is interesting though is that REAL64 data entries seem to behave a bit better - next time I'm building a user interface I might try them whenever I have a non-integer value to enter to see if they always work as expected.

Cheers,

Mike

Attachments

VEE Number Representation.vee1.6 KB

Actions

8 Replies

wangyiliu99 Sep 24, 2013 3:15 AM
Mark Correct
Correct Answer
sorry to bother again,

via searching this forum, I found the answer,

simply not use the
data>constant>real32,
but
data>constant>text

can solve this problem.

But would anyone help me with the case, while data is not input by the Text editor,
but from a *.txt file.
READ TEXT
command formats are quite a lot.

However, how could get 100.2 exactly 100.2, rather than 100.200000xxx

BR,
Yiliu
Like • Show 0 Likes0
Actions
- Mike @ wangyiliu99 on Jun 13, 2013 4:54 AM
  Mark Correct
  Correct Answer
  Yes this is a recurring theme - in my view this is a bug in VEE - others will tell you that it is correct because the underlying binary cannot exactly represent these numbers ( not quite true actually ) - but I think that if I enter 8.9 that's what should be printed, displayed etc.
  
  You have found the solution, use text for input and ensure you format numbers for output ( even that fails sometimes due to this 'feature' of VEE.
  
  Not sure if that is helpful, beyond "it's a known problem and you are dealing with it the same as the rest of us".
  Like • Show 0 Likes0
  Actions
  - wangyiliu99 @ Mike on Sep 24, 2013 3:15 AM
    Mark Correct
    Correct Answer
    Hi, Mike
    
    thanks a lot.
    
    b.t.w., do you know any function that could
    change data format say, string to real?
    Like • Show 0 Likes0
    Actions
  - wangyiliu99 @ Mike on Sep 24, 2013 3:15 AM
    Mark Correct
    Correct Answer
    Hi, Mike,
    
    would you please take a look at the snapshot of my VEE window.
    
    We could see that the ExpandDuringEdit is "False",
    but still we could see the value shown in yellow has so many digits.
    
    I am really so tired of this.....
    
    Anyone, please help!
    Attachments
    ExpandDuringEdit.JPG43.1 KB
    Like • Show 0 Likes0
    Actions
    - wangyiliu99 @ wangyiliu99 on Sep 24, 2013 3:15 AM
      Mark Correct
      Correct Answer
      after checking carefully about the properties of the Real32,
      I found the "NumFormatfor" property and snapshot is attached here.
      
      In this setting, the value displayed in the editor box is okay, however,
      when check its value by putting the mouse on the line, it is still with so many digits
      
      Yiliu
      Attachments
      NumberFormatfor.JPG35.0 KB
      Like • Show 0 Likes0
      Actions
      - Mike @ wangyiliu99 on Jun 14, 2013 3:22 AM
        Mark Correct
        Correct Answer
        You cannot format the tooltip or 'line probe' as it's called. I agree it is annoying.
        
        Regards, Mike
        Like • Show 0 Likes0
        Actions
        wangyiliu99 @ Mike on Sep 24, 2013 3:15 AM
        Mark Correct
        Correct Answer
        Hi, Mike,
        
        today I contacted agilent support Japan and got the problem solved.
        
        the method used is: (sample is shown for the case only one digit after the period)
        (1) 10 times the number
        (2) round that number to the nearest integer
        (3) divide that number by 10
        
        to get the say 100.1 exactly.
        
        Attached is the reference program.
        Enjoy
        Attachments
        SampleRound.vee5.0 KB
        Like • Show 0 Likes0
        Actions
        Mike @ wangyiliu99 on Jun 21, 2013 8:44 AM
        Mark Correct
        Correct Answer
        Unfortunately you've been duped! The functions you have used have converted the number to a Real64 which seem to represent your number in the way you'd like to see it ( and the way every other language does it ). I have attached a simpler example which does what you stated but if you hover over the line you'll see it is not the number I entered.
        
        I'm afraid that, like me, you'll just have to live with it and make work-arounds whenever you want to display or have a user enter a value.
        
        What is interesting though is that REAL64 data entries seem to behave a bit better - next time I'm building a user interface I might try them whenever I have a non-integer value to enter to see if they always work as expected.
        
        Cheers,
        
        Mike
        Attachments
        VEE Number Representation.vee1.6 KB
        Like • Show 0 Likes0
        Actions

SolvedQuestion about ExpandDuringEdit

Outcomes

Attachments

Attachments

Attachments

Attachments

Related Content

Recommended Content