 lvlib private members that are children of a public polymorphic |
|
|
|
|
Forum Rules
Please post topics into this forum that relate to specific features introduced in LabVIEW 8.x.x. The post will be moved to the appropriate forum if it does not meet this requirement. Your post may also be moved if it's deemed that it would fit better in another forum regardless. For example: LabVIEW OOP topics should go to the GOOP forum.
Tags |
(This content has not been tagged yet)
|
 ·
 ·
 ·
 ·
 ·
 ·
 ·
 ·
 ·
 ·
 ·
 ·
 |
 Jun 5 2008, 10:57 PM
Post
#1
|
|||
 I'm a LAVA, not a fighter.  V I Engineering, Inc.  Posts: 3754 Joined: 13-October 03 From: Michigan, USA Member No.: 181 Using LabVIEW Since:1993 LV:8.5 ,. ,. 
My Blog
 |
Wow - that's a mouthful!
 I'm just thinking out loud here: imagine I have a polymorphic VI (let's call it the "parent") which has some components (let's call them the "children") and I create a lvlib that contains both the parent and all it's children. Say I then set the children to private in the lvlib (you can probably see where I'm going here), but I leave the parent as public. Now I can't use the parent in a VI outside of the lvlib, because all it really is is a placeholder for one of it's children (which are private). Would it make sense to have private children of a public parent inheret the public attribute as a special case for polymorphic VIs only? -------------------- 
|
||
 |
 
|
||
| Ad |
Jun 5 2008, 10:57 PM
Post
#
|
||
|
|
|
||
|
|
|
||
|
Jun 5 2008, 11:59 PM
Post
#2
|
|||
 Very Active Premium Member  Posts: 218 Joined: 1-January 08 From: Perth, Australia Member No.: 10325 Using LabVIEW Since:2006 LV:8.5.1 ,8.6 ,.
|
Hi crelf
I came across the same thing when I wanted to design polymorhpic "tool" VIs and distribrute them in .lvlib but keep the internals private as the point was to encapsulate using polymorphism. As it kept breaking my code, which I thought was unintuitive, I haven't gone back for a second try. Maybe there is a reason for it? But if anyone knows a work around - I am keen to know! Especially now NI have starred using lvlib, I bet we see them around more and more in the future. The ability you described would sure be handy for source distribution. -------------------- all day...
|
||
|
|
|
||
|
Jun 6 2008, 02:21 AM
Post
#3
|
|||
 LV R&D Envoy NI  Posts: 1226 Joined: 15-August 06 From: Austin, TX Member No.: 5877 Using LabVIEW Since:2000 LV:8.5.1 ,. ,.
My Gallery
|
Yes, it would make a lot of sense to allow this for polymorphic VIs. Unfortunately, we didn't have the idea until late in the game and the architecture we use for testing scope has proven inflexible for making this work. It's a low priority desirable behavior.
-------------------- "A VI outside a class is a gun without a safety. Data outside a class is a target."
--- A message from LabVOOP R&D
|
||
|
|
|
||
|
Jun 6 2008, 03:09 AM
Post
#4
|
|||
|
I'm a LAVA, not a fighter. V I Engineering, Inc. Posts: 3754 Joined: 13-October 03 From: Michigan, USA Member No.: 181 Using LabVIEW Since:1993 LV:8.5 ,. ,.
My Blog
|
QUOTE (jgcode @ Jun 5 2008, 07:59 PM)  Especially now NI have starred using lvlib, I bet we see them around more and more in the future. I sure hope so! QUOTE (Aristos Queue @ Jun 5 2008, 10:21 PM) Yes, it would make a lot of sense to allow this for polymorphic VIs. Unfortunately, we didn't have the idea until late in the game and the architecture we use for testing scope has proven inflexible for making this work. It's a low priority desirable behavior. Thanks for the info Stephen - I figured as much. --------------------
|
||
|
|
|
||
|
Jun 6 2008, 04:51 AM
Post
#5
|
|||
 CCT It Premium Member Posts: 1337 Joined: 13-June 05 From: Woerden, Netherlands Member No.: 2399 Using LabVIEW Since:2001 LV:8.5.1 ,6.1 ,8.2.1 
My Blog
My Gallery
|
QUOTE (crelf @ Jun 6 2008, 12:57 AM) Wow - that's a mouthful! Would it make sense to have private children of a public parent inheret the public attribute as a special case for polymorphic VIs only? Good description, but I don't think it is possible. QUOTE (Aristos Queue @ Jun 6 2008, 04:21 AM) Yes, it would make a lot of sense to allow this for polymorphic VIs. Unfortunately, we didn't have the idea until late in the game and the architecture we use for testing scope has proven inflexible for making this work. It's a low priority desirable behavior. Let me bump this. Together with the same behaviour for typedefs. Ton --------------------
|
||
|
|
|
||
|
| Time is now: 2nd December 2008 - 02:21 PM |