didierj

Hi, Did someone successfully implement executables (built with LV) with icons that have more than 256 colors? Adding icons with e.g. microangelo seems not to work. My app isn't running anymore afterwards. Didier

Paul, Did you try to install the 6i Version of your DSC-package on LV7? It might work, I didn't do it. Just by copying the files wouldn't work because the DSC has a whole engine (with a database) running in the background. It is based as a client-server system. At least you'll need the whole client part (if the server with the database is running on an other machine). Didier

Dear Keith, I think the subject of good wiring rules is already well documented in all the forums but to my disappointment still not enough known (just got an instrument driver, Instrument price ~15'000$, and the code makes me cry!). - A good book is "LabVIEW Grphical Programming" from Gary W. Johnson and Richard Jennings, Mc Graw Hill books - Also good resources are the LTR (www.ltrpub.com) especially Volume 7, Number 1 and 2: main Topic "Rules to Wire By". a list of 44 rules of things to do and not to do in LV. - NI site to go further: http://digital.ni.com/public.nsf/3efedde43...07?OpenDocument Didier

I know about ActiveX and already used it several times. The problem there is, that properties and methods often require "strange" structs, instances, pointers to variables of whatever type, ... The great advantage of LV is, that data property is default and not hidden in a sub-sub-...-class of the control like the ActiveX ones. When I use ActiveX controls I often use more time to "decipher" the control than for wiring the whole rest of the program. Didier

I'm always disappointed, when I compare the frontpanel possibilities of LV and other languages like Delphi or so. In text based languages you find a huge ammount of different controls and combination of controls extending the features and possibilities of your program. One can rewrite the code or add code to an existing control it he need it. In LV one is restricted to the controls that NI permit the programmer to use. A first step towards custom control is made with the custom probe and subpanels. It would be nice to have these features implemented in controls. Features of custom controls should be: - having code behind your control - possibility to create events on the control - redirect standard events of the control to modify its behaviour - possibilities to combine controls (e.g. build a data navigator with "first","previous","next",... buttons - possibility to disable/extend context menu on controls (e.g. disable the ability to autoscale a graph or remove buttons on tool palette) Didier

Alex, This behaviour is not only in LV but "all" programming languages. Internally multiple dimension arrays are built this way: - each row of your 2d array is built as a separate 1d array containing the values of this row. the size of e.g. the first so created array is dimension M. - these arrays (or rows) are indexed in a separate array of pointers, each pointer pointing to one of the arrays mentioned above. the size of the pointer-array is the dimension N. Thus, a 2d array is an array of pointers pointing to a series of 1d arrays of whatever type - building a 2d array from empty 1d arrays gives you a dimension of Nx0. More complicated: a 3d DBL-array is an array of pointers pointing to arrays of pointers pointing to arrays of double values. Cheers, Didier

I see, I'll probably have to revise my source or upgrade... Thanks for the replies. Didier

I know the property node very well, but on LV 6.1 there is no such property on vi class. Didier

Hi, In the standard menu there is an "application item" that is named "page setup...". Because I have to build my application in a third language (that might not be the system language) I should either: - be able to change the the item name of this "application item" or, - create a "custom item" and run the "page setup"-panel programmaticaly. Does anyone know how to implement one of the two possibilities? Thanks, Didier