Omar Mussa Posted January 15, 2009 Author Report Share Posted January 15, 2009 I'm still using LabVIEW 8.2.1 for some of my projects and I just ran into a strange LVOOP bug. If you change the class description property (right click on class-->Properties-->Documentation) and press OK to close the dialog, the class will lose its inheritance information. I haven't tried this on a more recent version of LabVIEW to see if it was fixed. Is this a known issue? Is it there in 8.6? Its annoying because it breaks a lot of class member VIs if all of a sudden they are no longer in the same class hierarchy. I'm going to avoid documenting my classes for now. Quote Link to comment
Omar Mussa Posted January 15, 2009 Report Share Posted January 15, 2009 I'm still using LabVIEW 8.2.1 for some of my projects and I just ran into a strange LVOOP bug. If you change the class description property (right click on class-->Properties-->Documentation) and press OK to close the dialog, the class will lose its inheritance information. I haven't tried this on a more recent version of LabVIEW to see if it was fixed. Is this a known issue? Is it there in 8.6? Its annoying because it breaks a lot of class member VIs if all of a sudden they are no longer in the same class hierarchy. I'm going to avoid documenting my classes for now. Quote Link to comment
Aristos Queue Posted January 15, 2009 Report Share Posted January 15, 2009 I've never heard of this bug. I could not replicate it in 8.2 or 8.6. Is there something special about the particular class that you are updating? Quote Link to comment
Aristos Queue Posted January 15, 2009 Report Share Posted January 15, 2009 I've never heard of this bug. I could not replicate it in 8.2 or 8.6. Is there something special about the particular class that you are updating? Quote Link to comment
Omar Mussa Posted January 15, 2009 Author Report Share Posted January 15, 2009 QUOTE (Aristos Queue @ Jan 14 2009, 03:21 PM) I've never heard of this bug. I could not replicate it in 8.2 or 8.6. Is there something special about the particular class that you are updating? Not that I know of -- the class is fairly small. I'll try to reproduce it from another blank project. Quote Link to comment
Omar Mussa Posted January 15, 2009 Author Report Share Posted January 15, 2009 QUOTE (Aristos Queue @ Jan 14 2009, 03:21 PM) I've never heard of this bug. I could not replicate it in 8.2 or 8.6. Is there something special about the particular class that you are updating? Not that I know of -- the class is fairly small. I'll try to reproduce it from another blank project. Quote Link to comment
Aristos Queue Posted January 16, 2009 Report Share Posted January 16, 2009 Another NI employee who read this post has just let me know that, yeah, he saw something like that once, in LV8.6. He also cannot reproduce the issue, although in his case, it happened to many classes when he did some batch processing on them. This isn't enough info for me to even file a CAR much less debug the problem, but I'll keep my eyes open when I'm working on other CARs related to saving and/or property editing for problematic code snippets. Quote Link to comment
Aristos Queue Posted January 16, 2009 Report Share Posted January 16, 2009 Another NI employee who read this post has just let me know that, yeah, he saw something like that once, in LV8.6. He also cannot reproduce the issue, although in his case, it happened to many classes when he did some batch processing on them. This isn't enough info for me to even file a CAR much less debug the problem, but I'll keep my eyes open when I'm working on other CARs related to saving and/or property editing for problematic code snippets. Quote Link to comment
Omar Mussa Posted January 16, 2009 Author Report Share Posted January 16, 2009 QUOTE (Aristos Queue @ Jan 15 2009, 10:00 AM) Another NI employee who read this post has just let me know that, yeah, he saw something like that once, in LV8.6. He also cannot reproduce the issue, although in his case, it happened to many classes when he did some batch processing on them.This isn't enough info for me to even file a CAR much less debug the problem, but I'll keep my eyes open when I'm working on other CARs related to saving and/or property editing for problematic code snippets. I now have a workflow to generate the problem in LabVIEW 8.2. Still not tested in 8.6 but I'm going to guess that it still exists if nobody reported it in 8.2. Here is the problem -- if you modify the child class documentation property for a class whose parent class is not in the same project, then the child class will lose its inheritance info. Open the attached lvproj. Open 'my method.vi' -- notice it is executable. Now change the documentation property of the class and it will break the method. Please post the CAR here so I can track it. Thanks! Quote Link to comment
Omar Mussa Posted January 16, 2009 Author Report Share Posted January 16, 2009 QUOTE (Aristos Queue @ Jan 15 2009, 10:00 AM) Another NI employee who read this post has just let me know that, yeah, he saw something like that once, in LV8.6. He also cannot reproduce the issue, although in his case, it happened to many classes when he did some batch processing on them.This isn't enough info for me to even file a CAR much less debug the problem, but I'll keep my eyes open when I'm working on other CARs related to saving and/or property editing for problematic code snippets. I now have a workflow to generate the problem in LabVIEW 8.2. Still not tested in 8.6 but I'm going to guess that it still exists if nobody reported it in 8.2. Here is the problem -- if you modify the child class documentation property for a class whose parent class is not in the same project, then the child class will lose its inheritance info. Open the attached lvproj. Open 'my method.vi' -- notice it is executable. Now change the documentation property of the class and it will break the method. Please post the CAR here so I can track it. Thanks! Quote Link to comment
Aristos Queue Posted January 16, 2009 Report Share Posted January 16, 2009 QUOTE (Omar Mussa @ Jan 15 2009, 02:18 PM) Please post the CAR here so I can track it. Thanks! CAR 140811 Quote Link to comment
Aristos Queue Posted January 16, 2009 Report Share Posted January 16, 2009 QUOTE (Omar Mussa @ Jan 15 2009, 02:18 PM) Please post the CAR here so I can track it. Thanks! CAR 140811 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.