SuperS_5

I have not had any time to play with scripting before, and still don't. I am very excited about it though, so have been playing with this problem. I have found out how to connect a wire, in the case that you didn't want to delete the original control. However, apparently the seemingly easy way of deleting the wire segment, "is not yet implemented." (That is directly from the error cluster) Rewiring all of the segments after deleting the wire is the alternative.

good luck. Vision is very powerful and fast. Although expensive, it has been worth the $$ for us.

Sorry, I didn't look carefully enough. I see your problem now. The replace method does work though. Edit: Looks like we are racing

Hi, I have not had the need to create custom controls, and only poked at the concept, but it sounds like an application for X-Nodes. I think the better question is why is vision off the map? It is highly functional. I have used Vision before, and appreciate the hard work that went into it.

Hi, The VI as it stands seams to work for me. However, there is a method in the invoke node (replace) that makes the diagram simpler

I had a situation where I needed something like this, however, I found a good G code solution. I had a dll call that would spawn a new thread, and return immediately. The spawned process would continuously put data into an array that was provided to the dll by LV. The problem was that LV would de-allocate/reallocate the array memory space after the subVI calling the dll completed. This of course causes memory corruption problems. The solution was to use an uninitialized shifter for the array, prefilled to the desired array size. This allows the memory space to remain open, and no corruption errors.

Reproducable for me; however, case E was not reproducable. I am using LV10.0 and Windows 7.

I like the tree-polling solution. In one project, there was a multi-column list-box, I had to update the background colours of all of the items. (couple hundred rows and several columns!) Updating them would freeze the UI until done, which was bad. So I stuck all updates to be done into the shifter, (an array) and processed a couple of these updates at a time during the timeout case. I tweaked the number of cells to process, so that the total time was not too long, but the screen was still responsive. I had some logic for searching the array to ensure I didn't have multiple updates upon the same cell. The cells that I updated were determined by which cells where visible, and if all visible were OK, then process everything else. I am not sure if this would work in your case, if you are updating the values too quickly.

Are there any errors reported from the read segment? I would wire the error across to the write segment, insuring that the new file actually has valid data. (I am guessing that excel is blocking the reading of the file, while it is open)

+1 for MySQL. I use it a lot, although, I also like SQlite for local work. Database design is the name of the game here, but not too hard to wrap your head around once you nail down your delivables.

I use these shortcuts. When I have enough desktop space, I use it over my wallpaper.

The variant can be coerced to a string, or other data type if known. Data types can be pulled from the database if absolutely required.

ops forgot to take out the timing info for single threaded mode......ignore the timing part of that for loop.

Using parallel for loops will be faster if using large arrays and multiple processors.

Hi, I have been playing with SQlite for a little while, that a LabVIEW toolkit would be nice. However, for the moment, I would not use it for any of my current customers, and would only be for "learning" and proof of concept purposes. I, therefore, request a "community" or "educational" version that would allow for use of the toolkit past your trial period, but not for commercial uses.

This is somthing that I would use. If i needed somthing to update/blink/do anything on the FP above this, while hiding your work, I would have 2 options. 1) place this VI into a subpanel, and call it, while placing the updating element on the parent. It would be extra work on the subpanel, and a little more challenging from a design point of view. 2) make a pop-up thats greyed and somewhat transparent. (I am leaning here if the cover Boolean won't work) I like the KeepItSimple method, but your requirements will dictate your choice. PS: VI is saved in 8.6 disabled grey.vi

I perfer setting the mouse busy, although, I also use "cover booleans" to disable the front pannel. The boolean is a classical boolean, coloured transparent. It is then set visable/invisable via the property node whenever needed. This is a very quick/low resource method to disable/colour many items on the FP. I have also used it to display simple text messages, (boolean text, coloured) while disabling and graying the FP.

I don't use FPGAs much personally, however, I do work on a very large project. We also use the project explorer to with tortoise SVN without much issue. Producing notes/internal documentation is very important however! Collisions with the lvprog file can be common, but, we don't edit that file manually much. We, therefore, simply overwrite the lvprog file with the modified version we require. I am not sure how much changes that you will actually make in the project explorer with FPGAs. Using a LabVIEW version before 2010 can cause a lot of conflicts because of "recompiling," however, this is overcome by good documentation, and only committing the files that you actually changed. Every little while, we will commit a "recompile" with specifically only recompiled files, (after committing real changes) and enforce SVN "comments." Mike

Trying to open a reference to the file also fails with the same error.

I have see somthing with a simular result. Mine was on LabVIEW 8.6.1. Mine seamed to be a block diagram corruption, but would reappear randomly. I think we had to copy the code into new vi to replace the problem vi. Anyways, I just had to try this one out to see if it was the same problem. Although it is not the same problem, it appears that the invoke node is not giving the correct data. The output of a "to variant" node is not the same as the output of the property node. Selecting "Show Type" (right click menu) of a variant control/indicator gives this output: "invoke node" 'FP References': cluster of 18 elements 'Run': Boolean Refnum '': void 'Loop': Boolean Refnum '': void ... "to variant" 'Value': cluster of 18 elements 'Run': Boolean Refnum '': boolean (TRUE or FALSE) 'Loop': Boolean Refnum '': boolean (TRUE or FALSE) 'Abort': Boolean Refnum ... I am curious if this has anything to do with it.

i personally use Hamachi most situations where we need to connect computer across the internet. It requires little setup, and uses encryption by default. It requires both computers to have the client installed, and running, and be authenticated. I find it very useful to negotiate networks that employ NAT. You would need administrator rights to install it, also IT departments may still block it's ports, permission would still be required. (BTW: it has a free fully functional "non-commercial" version) Mike

Thanks, using these settings in the LabVIEW environment helped me a lot. I will also be adding these to my program ini files as well. I totally forgot about these settings, I was starting to hate the "windows classic" theme. Mike

Hi, It seams that you have a type mismatch here. I have not noticed this behavior before, but LabVIEW ignores the conversion if no output is wired. If a scaler (single string) is wired to the type input of the "variant to data" function, there are no errors. This could be caused because there is no data on the variant "value2". I usually use the report generation tool kit. It has functions for this kinda of work. Mike

Hi, I can't help much about converting the above tools to 64bit, but this is a copy and paste of a note from that very web-page that you posted. "The abilities of the VI Server supersede the functionality of the VIs. National Instruments recommends that you use the VI Server functionality for new applications. Implement calls that the VI Server does not support through the Windows API directly by using a Call Library Function node in a more recent version of LabVIEW." Would porting your code to use native LabVIEW functions be possible? That would be my first option to investigate. Mike

Hi, I think an event structure is the only way to always get the last key pressed. I would simply put that data into a shifter or stack. There is a VI to poll the keyboard, however, it will not return the last pressed keys, only the currently pressed keys. This means that you would have to continuously poll the keyboard. I think a good question is, why is an event structure not usable? Mike