By apoorve kalot
just following a tutorial on YouTube [https://www.youtube.com/watch?v=Ko0heNZhRvI], for setting objects in lab-view for simulation, doing the steps as stated. as program executes, the resultant spheres, ( which has been added to the 3D picture object, are very far out zoomed ) , done the following steps to correct it, still no help
1) seen online help of using "shift + drag" to correct it, but it's still no help,
2) changed camera position to : none and auto - redraw, still no help,
since i am new to this, it is request to state the measure to correct the problem and to avoid these problems.
Along with one question : how to add Co-ordinate axises for reference to it, independent of any other objects, [ i.e. the axises shouldn't be affected by rotation, translation or objects ] in 3D picture object
edit : same question is posted as well on : https://forums.ni.com/t5/LabVIEW/camera-postion-stuck-in-3D-picture-control/m-p/3990030#M1138526
My concern is about object based framework.
I'd like to talk about a "sensitive" subject, which divides people around me.
I'm sure there are a plenty of objects aficionados here.
A few years ago, LabVIEW give us the first object based template : the Actor Framework, which is certainly powerfull
When I conduct Core3 training, I'm tempted to show what could be an object based framework in LabVIEW, then I remember how the actor framework looks, then I decide to make my trainies continue to use LabVIEW, and finally I don't show the actor framework.
When will NI provide a SIMPLE object based framework in the TEMPLATES ?
Something like the command patern exposed here by Elijal Kerry :
or in a the test executive example of the PTP sequencer :
I still use the "old" QSM (please Daklu, don't bite me), for sure it is not an ideal solution...
I love objects, I used them a lot in my code, but not currently for my high level code.
Any links or suggestions ?
Next week I am teaching a LVOOP course and my students use TestStand a lot and I expect to get questions regarding the use of LVOOP and TestStand. The things I have heard are:
- TestStand does not recognize LVOOP Objects, so the developper has to flatten the Object Reference to string and then pass the string to TestStand, and viceversa, if they get the flattened Object they need to unflatten to string in LabVIEW: http://digital.ni.co...62573A9004C5A07
- Dynamic dispatch is lost
Are there any other tips/tricks/myths I should be aware of?