search

opengds / OpenGDS

Open GOOP Development Suite
MIT License
54 stars 14 forks source link

labview 2020 64 bit #63

Closed 158545614 closed 3 years ago

158545614 commented 3 years ago

create read/write method VI name is not correct

1

MikaelHolmstrom commented 3 years ago

Is that using the latest Beta Build (v1.2.54)? I haven't been able to reproduce it yet.

MikaelHolmstrom commented 3 years ago

I found another bug and I've added .vim creation support. But I can't replicate this error :-(. Can you send my the class example?

158545614 commented 3 years ago

Desktop.zip

2

this pitcure show the other bug?

1 what is the differences about these two method？ they seem to both can read/write attributes。which one is better？

MikaelHolmstrom commented 3 years ago

Interesting...

158545614 commented 3 years ago

Interesting...

Do you reproduce these bugs？

158545614 commented 3 years ago

Interesting...

Hi Do you replicate these errors??

MikaelHolmstrom commented 3 years ago

I've not found the issue yet. You can always help he out and probe some values in the VI: C:\Program Files (x86)\National Instruments\LabVIEW 2020\resource\Framework\Providers\Open_GDS\ClassProviders\Provider_LvNativeClass\ClassWriterNative_class\DialogCreateMethod.vi ...to see what's going on. To debug this VI (or any OpenGDS VIs), open the VI, enable "Allow debugging" (VI Properties/Execution), add a Break Point on the BD in the VI and save it. Then restart LV and when this VI gets called the BD will open and you can debug it. After the VI gets closed, the debugging stops working so to debug it again, you have to restart LV and repeat the process.

MikaelHolmstrom commented 3 years ago

BTW regarding the Property Method:Get/Set or Property Node:Read/Write, if you use the Property Node:Read/Write, you can read and write object attribute values using a standard Property Node VI (QD: rn). You could of course use thee Read/Write VI as normal SubVIs but that's not their intention.

158545614 commented 3 years ago

BTW regarding the Property Method:Get/Set or Property Node:Read/Write, if you use the Property Node:Read/Write, you can read and write object attribute values using a standard Property Node VI (QD: rn). You could of course use thee Read/Write VI as normal SubVIs but that's not their intention.

I've not found the issue yet. You can always help he out and probe some values in the VI: C:\Program Files (x86)\National Instruments\LabVIEW 2020\resource\Framework\Providers\Open_GDS\ClassProviders\Provider_LvNativeClass\ClassWriterNative_class\DialogCreateMethod.vi ...to see what's going on. To debug this VI (or any OpenGDS VIs), open the VI, enable "Allow debugging" (VI Properties/Execution), add a Break Point on the BD in the VI and save it. Then restart LV and when this VI gets called the BD will open and you can debug it. After the VI gets closed, the debugging stops working so to debug it again, you have to restart LV and repeat the process.

WJ$@@PR~_ZFARH }K5$JENE

Did you open this project? is it correct??

MikaelHolmstrom commented 3 years ago

There is no issue with the project when I use it?!?!? image

158545614 commented 3 years ago

There is no issue with the project when I use it?!?!?

W4NF_0JG696TN6VC@{( A9C

I find this _property ctl seems not correct. what is the problem?

158545614 commented 3 years ago

There is no issue with the project when I use it?!?!? image

3R9WW__9$NB5KP1}2Q`NAGS

it seems labview'bug??