LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

FP Origin property in LV 8.5

What happened to the Frfont Panel Window --> Origin property in LV 8.5? Smiley Surprised
 
I m unable to find it... Smiley Sad
 
Can anybody please tell me if it has been moved somewhere else?
- Partha ( CLD until Oct 2027 🙂 )
0 Kudos
Message 1 of 11
(4,215 Views)
It's a property of the pane.

Ton


Message Edited by TonP on 03-05-2008 07:42 AM
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
Message 2 of 11
(4,207 Views)

Thanks, Ton. Smiley Happy

Do you know the reason why the explicit Pane property node throws error saying that "Object reference is invalid", if it is referenced by a Class Specifier Constant?

Earlier, in LV 7.1, the explicit property node for a VI FP Origin used to work without being referenced with a Class Specifier Constant or a Open VI reference. Smiley Happy

I dont understand why it has been changed in LV 8.5 for both Panel & Pane explicit nodes. Smiley Surprised

- Partha ( CLD until Oct 2027 🙂 )
0 Kudos
Message 3 of 11
(4,197 Views)
Hi Ton,
 
Atleast, I can understand that there can be many panes, but anyhow, it is going to be only one FP in a VI.
 
So, why again to refer to it when it is already an explicitly known thing, like that of a VI's property node... ?! Smiley Surprised
 
I m bemused. Smiley Indifferent
 
Or, am I not getting it correct still? Smiley Sad
- Partha ( CLD until Oct 2027 🙂 )
0 Kudos
Message 4 of 11
(4,194 Views)

 

This wouldn't have worked in older versions either. My guess would be that this was done to save the programmer from making mistakes. Using the current application and current VI as default is reasonable, but if you do this for too many classes you might get bugs if people forget to wire a reference into the property node.

The error itself should be obvious in this case - the constant reference is not a reference to the current VI's panel, but a generic reference to the Panel class.


___________________
Try to take over the world!
Message 5 of 11
(4,176 Views)

If the FP Window Bounds Property is kept in its old place intact, then why has the FP Window Origin Property alone been moved into the Pane class? Smiley Surprised

If FP Window Bounds is NOT based on the Pane class, what is the reason behind the FP Window Origin being based on the Pane class? Smiley Indifferent

Why I m asking this again is because, the origin for a FP is going to be only one irrespective of the no. of panes you re going to have in your VI, like the FP WIndow Bounds. Smiley Happy

May someone explain me more of this, if my understanding on the subject is incorrect... Smiley Wink

 

- Partha ( CLD until Oct 2027 🙂 )
0 Kudos
Message 6 of 11
(4,128 Views)
Panes are a pain.  I still look for the origin in its old place, but NI made origin a property of a pane and panels are just containersfor one or more panes.

Message Edited by falkpl on 03-18-2008 09:41 AM
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA
0 Kudos
Message 7 of 11
(4,119 Views)


parthabe wrote:

If the FP Window Bounds Property is kept in its old place intact, then why has the FP Window Origin Property alone been moved into the Pane class? Smiley Surprised


It's not the window origin, and in fact it never was. It used to be the panel origin, where the panel was the part of the window you could place controls in. When panes were introduced it became the pane origin - each pane can have a completely separate origin.
 
As for the Window Bounds property, without really thinking about it I would say that it remained as a VI properties because it controls the size of the actual window - you can't have a window where different panes which are near each other have different heights.

___________________
Try to take over the world!
0 Kudos
Message 8 of 11
(4,109 Views)

tst,

I think it was the FP Window origin in LV 7.x. Smiley Happy

See the attached pic. Correct/explain me if I my understanding is wrong.

- Partha ( CLD until Oct 2027 🙂 )
0 Kudos
Message 9 of 11
(4,089 Views)
OK, whether or not it should have been a Panel class property or a VI property is a good question and the answer could probably go either way, but the concept remains the same - when there were no panes, there was a single origin. With panes, each pane can have its own origin.

___________________
Try to take over the world!
0 Kudos
Message 10 of 11
(4,074 Views)