PJM_labview

Another possibility (convoluted but it should work): Create a SubVI that does the following: Create a batch file in windows temp folder (reuse the same name every time so you don't end up creating many batch files ) that will wait a bit (1-2s) before deleting your ini file. Execute this batch file using system exe (non blocking). Note: you should run this SubVI as the last operation you do before exiting your app. PJM

I guess anything "express" is too fast for a cow PJM

QUOTE (Cat @ Apr 13 2009, 11:32 AM) Ouch! PJM

Post what you have so we can give you better feedback. PJM

I strongly agree with AQ. Turn that flag on and this will save you a lot of future headache. This is one feature I really missed when I have to code back in older LV version. PJM

QUOTE (Aristos Queue @ Apr 6 2009, 09:21 PM) On can argue that this is pretty much restricted to NI employee that are familiar with the VI (and all its siblings) file format.

QUOTE (Cat @ Apr 3 2009, 11:06 AM) And the beauty of having it in a frame of the state machine is that the day you need to call that init frame back (when not doing per say an init step [this does occurs on occasion especially for UI stuff]) you can easily do that without creating duplicate code. PJM

Add it manually from the additional installer section of the build script PJM

QUOTE (Aristos Queue @ Mar 26 2009, 04:20 PM) Would that be the DFIR (Data Flow Intermediary Representation) stuff that Jeff K. talk about in last year NIWeek keynote presentation? Anything you could share with us? PJM

I can replicate this. This is definitively a bug. PJM

I will do option c. c. Get someone else to do it for you. What that mean is that your business is "LabVIEW-based consulting" not maintaining servers, update it, patch it, protect it and so on... So I would advise to host all your code with a web hosting company so you can focus on your LabVIEW jobs. PJM

I don't thing there is any native way (opcode) that can do that (I wish there was though). I think you will have to implement it yourself using one of the various algorithm available out there (Ex: Antialias: Wu Algorithm). PJM

QUOTE (flarn2006 @ Mar 21 2009, 01:29 PM) No need to remove the password to find out whats happening in Picture to Pixmap. It is calling inside LabVIEW.exe the export function PictToPix (see image below). http://lavag.org/old_files/monthly_03_2009/post-121-1237682015.png' target="_blank"> PJM

QUOTE (ldindon @ Mar 12 2009, 02:54 AM) Very nice gauge (I especially like the anti-alias). This is funny, I wrote something quite similar about a month ago. PJM

Congratulations Tomi. Best of Luck to you and Agile 4. Philippe

In my previous job, I used to work on rapid prototyping systems. I wrote several control system app for different type of custom made hardware. In any case, welcome to the LabVIEW world. PJM

QUOTE (jdunham @ Feb 25 2009, 04:07 PM) I actually do not mind the "(no error)", but I do mind the size of the error cluster. I change them back to the size they use to be in older LV version (significantly smaller) suing the same procedure Jason described. PJM

I think that general benchmark should also be considered. Benchmark to consider: Memory footprint for a given app. Last year, one of my customer did not switch to LV 8.6 because a very large LVOOP app (> 5k VIs) was using a significant larger amount of memory than the same app in LV 8.5 (I dont remember for sure but I think it was in the order of 20% more). Other general benchmark (for a given app): Start time, Shutdown time (again with large app this could be very long...) . Something else that I would like to see (but I am sure that this is probably exotic for most people) is a benchmark on the rendering speed of images (object [square, rectangle, circle, text ....]) draw in the classic picture control. PJM

Use an XY Graph and change the scale to Zoom in or out. PJM

Here is a pure G example using VI server FP.Windows Bounds and user events (this is choppy when the windows moved fast). Download File:post-121-1233280932.zip LV 8.2 PJM

I think the annoying message is "resetting VIs" (that little dialog that show up in the upper left corner of the screen). I have seen this happen, but mostly when closing an application and most of the time it was on Linux. I rarely see this on windows. PJM

QUOTE (Aristos Queue @ Jan 22 2009, 11:06 AM) QUOTE (Ton @ Jan 22 2009, 12:39 PM) I only remember TDMS incompatibilities between the RTE's of 8.20 and 8.2.1. Ton Thanks for the info, this is a relief. Unfortunately the system is away in the field and the customer does not have real time spare chassis to test on. The software does not use TDMS. The only "fancy" thing used in this setup are share variables. Everything else is pretty standard LV. Thanks again. PJM

Hi, I have a customer that has software deployed on the field on a device that has a Compact Field Point and a PXI realtime chassis. Currently the software was build using LabVIEW 8.20. I am planning to send them an executable made with LabVIEW 8.2.1 and I am wondering if this can be done seamlessly (without having the user update the RT engine)? Basically can an exe made with LV 8.2.1 run on a 8.20 real-time device? Thanks PJM

This is indeed a very interesting control. My bet is that somebody at NI made it. PJM

QUOTE (normandinf @ Jan 16 2009, 07:32 PM) I see that you use the input VIs to solve this issue. Unfortunately, I need a cross platform solution and the input VIs do not exist on Mac. Note: If I can not find another solution, I will use this. QUOTE (Darren @ Jan 16 2009, 09:10 PM) In LabVIEW 8.6 there is a private event called "Shortcut Menu Dismissed". There's also the equally-handy "Operate Menu Dismissed" that fires when you dismiss the operate menu of a ring, enum, etc. -D This is good to know. Now I just have to figure out how to do that in LV 8.2... I found a way to get at the "click outside of LV" info. I create an asynchronous VI with both attributes of "floating" and "hide when LV not active" set to true. When this VI "FP.State" becomes "hidden" I fire a user event that tells me that LV has becomes "inactive". Now I am left with trying to find out whe the user escape out (press ESC) of the Run-time Shortcut Menu.