Jump to content

Use of TrollTech's Qt in LabVIEW

Recommended Posts

QUOTE(Jim Kring @ Jan 21 2008, 09:10 PM)

Not very likely for LabVIEW's UI widgets itself. Porting the existing widget code they build themselves since LabVIEW 2.5 on the various platforms to Trolltech would be a complete horror with many bugs, and functionality they simply can't implement on top of Trolltechs QT.

It seems to be related to some of the configuration utilities that got added recently. There is a http://forums.ni.com/ni/board/message?board.id=170&message.id=276416&requireLogin=False' target="_blank">thread on the dark side about it, where someone had troubles with it since his external code (Surround SCM) was using a different version of QT that clashed with the one LabVIEW was using. Apparently the Multi-Variable Editor is the whole story why QT is used and that is in essence a DSC feature only. However as that thread shows the QT libraries are loaded into the LabVIEW process independant if the DSC system is used or not. Why they wouldn't write the Multi-Variable Editor as LabVIEW Vi is a bit beyond me though. LabVIEWs widget tools are quite up to par with QTs.

Rolf Kalbermatter

Link to comment
  • 4 weeks later...

QUOTE(brent99 @ Feb 22 2008, 05:08 PM)

I saw that, and just assumed that Labview IS written in QT (at least as of v6.0 or so). No?

No definitely not! The entire UI widgets have been written for LabVIEW 3.0 from scratch based on the drect windowing API of the spcific platform (X11,Windows GDI and Mac OS QD) and that hasn't changed at all until now. The only real modification was with the adding of the 3D types of controls in LabVIEW 6, but they are based on the same proprietary object model that is used for the other built in LabVIEW widgets.

QT appearently only is used for the Multiple Variable Editor that is part of the LabVIEW Data Logging and Supervisory Toolkit, but since the LabVIEW installations contains that anyhow (but the according license is necessary to enable that functionality) it comes with every standard LabVIEW installation and since it is in the executable directory, Windows will always prefer to load those libraries if some component such as the SCC API provider for said system needs to load those libraries with that specific same name.

Rolf Kalbermatter

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.