Labview icons - smaller - nicer

[Pawel Pocwiardowski]

I think we should stress him to tell how to do it :))

PP


liao wrote:
>
> How do you know they are not! Any VI can be turned into something like
> "increment" function, which can be opened. One NI engineer said that,
> but he didn't say (or didn't want to say) how.
>
> Nadav Chernin wrote:
> > Hi, Pawel
> >
> > increment or multiplier are not VI's. This is built in LabVIEW code,
> > exactly as images of different LabVIEW structures or wires.

[wiebe@CARYA]

Hi,

It's not difficult to do, but you'll have to know LabVIEWs internal data
structure. Every object has a bounding box, a hotpoint, etc. Ni knows this,
the made it up...

For us to figure out how to do this from the compiled code, and VI data
structure, is very hard. One has to make a "VI parser", and change the
correct bits, to the correct values. It can be done, but it's hard to
automate. Also, the bounding box surrounding a VI is stored in the code that
uses the VI, not in the VI itself...

To implement this as a feature, NI could change the source code of LabVIEW,
and this whould be relatively easy for NI.

An effort from NI to implement this, doesn't seem very likely to happen (to
me). It might s
eem ideal to be able to do this, but there are down sides to
it. But you never know...

Regards,

Wiebe.





"Pawel Pocwiardowski" wrote in message
news:3D40E1FC.2E78ED4F@poczta.onet.pl...
> I think we should stress him to tell how to do it :))
>
> PP
>
>
> liao wrote:
> >
> > How do you know they are not! Any VI can be turned into something like
> > "increment" function, which can be opened. One NI engineer said that,
> > but he didn't say (or didn't want to say) how.
> >
> > Nadav Chernin wrote:
> > > Hi, Pawel
> > >
> > > increment or multiplier are not VI's. This is built in LabVIEW code,
> > > exactly as images of different LabVIEW structures or wires.

[Pawel Pocwiardowski]

Yes, they are keeping some trick only for them. Well, it sounds
resonable :).

regards
PP


"Wiebe@AIR" wrote:
>
> Hi,
>
> It's not difficult to do, but you'll have to know LabVIEWs internal data
> structure. Every object has a bounding box, a hotpoint, etc. Ni knows this,
> the made it up...
>
> For us to figure out how to do this from the compiled code, and VI data
> structure, is very hard. One has to make a "VI parser", and change the
> correct bits, to the correct values. It can be done, but it's hard to
> automate. Also, the bounding box surrounding a VI is stored in the code that
> uses the VI, not in the VI itself...
>
> To implement this as a feature, NI could change the source co
de of LabVIEW,
> and this whould be relatively easy for NI.
>
> An effort from NI to implement this, doesn't seem very likely to happen (to
> me). It might seem ideal to be able to do this, but there are down sides to
> it. But you never know...
>
> Regards,
>
> Wiebe.
>
> "Pawel Pocwiardowski" wrote in message
> news:3D40E1FC.2E78ED4F@poczta.onet.pl...
> > I think we should stress him to tell how to do it :))
> >
> > PP
> >
> >
> > liao wrote:
> > >
> > > How do you know they are not! Any VI can be turned into something like
> > > "increment" function, which can be opened. One NI engineer said that,
> > > but he didn't say (or didn't want to say) how.
> > >
> > > Nadav Chernin wrote:
> > > > Hi, Pawel
> > > >
> > > > increment or multiplier are not VI's. This is built in LabVIEW code,
> > > > exactly as images of different LabVIEW structures or wires.