Leaderboard

With LabVIEW 7.0 this is basically no problem. The functions to deal with .ico files are available in LabVIEW since about 6.0. Checkout vi.lib/platform/icon.llb. That are the same functions used by the application builder to read ico files as well as replace icon resources in the build executable. In LabVIEW 7.0 you also have a VI server method to retrieve the icon of a VI. Together these two things are all which are needed. There are however a few fundamental problems. The function to replace icon resource data works directly on the executable image (well really on the lvappl.lib file, which is an executable stub which is prepended to the runtime VI library and which locates the correct runtime system and hands the top level VI in that library to the runtime system). As such it can only replace already existing icon resources as doing otherwise would require relocating the resource table and its pointers, an operation which is very involved and error prone. Windows itself doesn't have documented API functions to store resources into an executable image, as this is a functionality not considered necessary for normal applications. lvapp.lib contains only icons for 16 color and 2 color icons for the size 16*16 and 32*32. Wanting to be able to have other icons would mean to add first those resolutions and sizes to lvapp.lib and improving the icon functions in icon.llb to properly deal with those extra resolutions. This is not really difficult to do. A different problem is that LabVIEW icons are always 32*32 pixels whereas Windows really needs 16 *16 pixel icons too, for displaying in the left top corner of each application window as well as in detail view. Rolf Kalbermatter

Update on the pricing changes. A Vision Development Module deployment license used to cost $440 ($110 with Academic discount). The new price appears to be $582. Now, since I am in Academia, the price that I see is different: This was a bit of a shock to me (remember, it used to cost 4 times less), so I tried to look for alternative sources of information. The page for quotes has a a phone number (which I called, more on that below) and an online quote link, which I followed. Being logged in as a duly registered academic user, the resulting quote specified that an Academic Discount was applied: Yet the price appears as $582. Which one is correct? I called. Long story short, the guy on the other end of the line did not know, then knew it was $582, but then when I mentioned that I had seen $407.40 on one of the page realized it was $407.40 and when I mentioned that the quote I had requested online showed $582, told me that then it would be $582. When I tried to explain that this was at the very least confusing and additionally looked like a rip-off, he simply hanged up. I am ambitiously engineering my replacement to the small part of the VDM I was using before I complete my migration to Python....