Jump to content

Mellroth

Members
  • Posts

    602
  • Joined

  • Last visited

  • Days Won

    16

Everything posted by Mellroth

  1. Why couldn't LabVIEW itself use a temporary build location and then copy the build to the specified location? Relying on users to put builds in a certain folder just because Windows/LabVIEW has a problem with long file paths, is not that nice. The application might build just fine on my system, but not on my colleagues system, just because his name is X characters longer than mine. A temporary build location, could also help when the build destination is within a SCC hierarchy, where some destination files are locked. In LV <8.6, LabVIEW builds everything just fine, then it might complain that the files are write protected, and throws all build files away. With a temporary location, LabVIEW could prompt the user to fix the destination problem, instead of throwing the build files in the trash /J
  2. When you find a gap, do you need the start location, stop location or the centre location (or do you need all of them)? /J
  3. QUOTE (Darren @ Jun 11 2009, 05:01 PM) I tried converting your code to read U32 values instead of a string, and I also removed the "Get File Position" and "Set File Position" functions. By this I was able to reduce the time, by approximately 30%, for large files. /J
  4. QUOTE (finimits @ Jun 9 2009, 04:46 PM) Sure, just use the methods from the "Model interface" palette to interface the model dll. /J
  5. QUOTE (pete_dunham @ May 5 2009, 02:36 AM) Hi, I don't know what you are trying to do, but I would typecast the control reference to a strict boolean directly. My guess is that this is better both in terms of performance, and memory. And, if you know that all your elements are booleans, you could typecast the array of references directly into an array of strict booleans, before entering the loop. http://lavag.org/old_files/monthly_05_2009/post-5958-1241530862.png' target="_blank"> /J
  6. QUOTE (manojba @ Apr 29 2009, 09:00 AM) How about this; 1. detect mouse click on the link text (easy to do with the event structure) 2. launch default browser as Antoine suggested, or you could embed the webpage in your application using an ActiveX container. /J
  7. QUOTE (Tim_S @ Apr 21 2009, 09:03 PM) I very much believe so, but again, I might be missing something in your setup. If you have the LabVIEW project correctly setup, you can compile the FPGA code using your local machine as compile server. I'm at home at the moment, and I just tried a compilation on a virtual FPGA setup, running in a VirtualMachine (within VirtualBox on an iMac). This worked as expected. /J
  8. QUOTE (Tim_S @ Apr 21 2009, 08:30 PM) Tim, Maybe I'm missing something, but we have compiled many updates for our remote systems (even more remote than Detroit - Brazil), without the actual units. Compilation has been done both for the RT parts as well as the FPGA. Have you tried to build the rtexe and compile the bit files on your local machine? Do you get any errors during the builds? /J
  9. QUOTE (Thang Nguyen @ Apr 20 2009, 04:55 PM) You should probably initialize the "EXIT?" boolean to FALSE before you enter the loops. /J
  10. QUOTE (Black Pearl @ Apr 14 2009, 09:16 AM) It is possible to configure the SVN server to only accept users in a domain to access the server. Then you can restrict each repository on the server to only allow access for a subset of these domain users. It is also possible to set permissions (by adding hooks), for a repository so that only a few users can add data to the /tags hierarchy, while granting "read access only" for all other users. /J
  11. QUOTE (labc @ Apr 14 2009, 08:16 AM) The data 1 might be equal to data 2 in terms of values, but the representation is different. Notice the red dot when you write data to the data 2 terminal, this dot represents a coercion, i.e. a conversion between one representation to another. I have not opened the code, but my guess is that when you write data to the new zip file, you are actually writing data as I32 values, not U8. The solution would be to specify the data type when you are converting from string to numeric. /J
  12. QUOTE (BrokenArrow @ Apr 6 2009, 09:38 PM) Since more than one application might share a resource like the COM port, I think it is good practice to setup the communications within your application, instead of relying on the "global" settings. My 2c /J
  13. QUOTE (Chris Davis @ Feb 7 2009, 08:45 PM) :worship: I was just starting to search for something like this. As always, LAVA is the place the look... /J
  14. Mellroth

    Alfa String

    QUOTE (alfa @ Jan 14 2009, 09:22 AM) Could you explain in more detail about these half-cannibals? Does it count as cannibalism if you are eating people that are at animal level? Also, do you think people at animal level eating other people should count as cannibals? /J
  15. QUOTE (george seifert @ Oct 28 2008, 02:32 PM) It is possible directly in LabVIEW. 1. Use an event structure and filter the event "Drag Starting?" 2. in this event, find the drag data named LV_TEXT 3. convert the drag data from variant to string, and then to a path 4. add an additional drag data element with drag data set to the path, and set drag name = LV_PATH http://lavag.org/old_files/post-5958-1225226246.vi'>Download File:post-5958-1225226246.vi /J
  16. Mellroth

    Alfa String

    QUOTE (rolfk @ Oct 24 2008, 08:37 AM) Your point was directly proved to be true :laugh: QUOTE (alfa @ Oct 24 2008, 09:10 AM) Looks like nobody is against prostitution!!! The 98% are afraid of prostitutes, that's why we have dictators, corruption... /J
  17. QUOTE (Altobo @ Oct 21 2008, 03:04 PM) Welcome to LAVA Altobo. You'll have to provide a lot more details to get the information you need, like 1. What kind of engines (SW process, physical engine, ...)? 2. What kind of interface do you have for your engine control? (serial, TCP/IP, UDP, ...) ... You are also going to get a lot more answers, if you show some effort and upload what you have done so far. /J
  18. QUOTE (ikd @ Oct 21 2008, 10:59 AM) Sounds like a timing issue. Try to put a msWait node after you have configured the serial port, i.e. don't send your commands directly after the config. /J
  19. QUOTE (d_nikolaos @ Oct 14 2008, 10:13 AM) The output is a 16bit number. To change the order of the Hi and Low bytes, just wire the node in different order. Use the LabVIEW contextual help to display how a function is used. /J
  20. QUOTE (d_nikolaos @ Oct 14 2008, 08:32 AM) As jdunham said, it would really help if you could post some code. To combine two 8 bit numbers into one 16bit number, you can use the "Join Numbers" primitive in LabVIEW. I don't know if you transfer the data in network byte order, or intel byte order, but you can handle either case with the "Join Numbers" /J
  21. QUOTE (normandinf @ Oct 1 2008, 02:52 PM) They can actually be dropped directly on the BD. /J
  22. Mellroth

    Alfa String

    QUOTE (alfa @ Oct 1 2008, 09:07 AM) Seems like a very bad statement. Check the mirror , then go checkout http://www.darwinawards.com/. QUOTE Honoring those who improve the species...by accidentaly removing themselves from it! /J
  23. QUOTE (crelf @ Sep 26 2008, 07:26 PM) Sorry, I meant copy-delete, and I was wrong in that the history is preserved, but there are still issues with the rename operation. http://subversion.tigris.org/issues/show_bug.cgi?id=898 QUOTE (PJM_labview @ Sep 26 2008, 07:33 PM) If by CLI you mean Command Line Interface, then do you know that you can automate TSVN by passing command to tortoiseproc.exe? Yes I knew that, but as I understand, not all SVN commands are exported in tortoiseproc.exe (and will most likely never be). Apart from that, I prefer to have the CLI commands to be the same on all platforms. Don't get me wrong, I voted for a switch to SVN, but I think all tools (CC as well as SVN and others) have some problems/issues. Depending on what platform you are used to, you will probably see different problems, just because you have a certain work flow in that old tool. /J
  24. QUOTE (lavezza @ Sep 26 2008, 07:48 AM) I can share as much as I remember right now, and I'll see if I can post some more info next week when I'm back in office. Our group have happily used ClearCase for the last 12 years, but are now moving over to SVN to have the same tools all over the company. What I did was to see if the methodology we used with ClearCase could be transferred to SVN without too much problems. To summarize; Yes! but with some changes in how we use labels and also some changes to our CM-plans Have a nice weekend /J The Pro's and Con's I remember right now; Pro' Clearcase * We really like the ConfigSpecification files, since they make it easy to backup to a specific revision, and still keep track of all linked module versions * Very Robust, we have never had any problems whatsoever * Dynamic views can be great, once you know how to use them, e.g. I can setup a specific view for a build. At the same time I apply my cs-file, all other users will see the same code as I do. * Labels are easy to apply, and easy to find. The user don't have to specify where to store a specific label, c.f. tagging in SVN * Very easy to switch between labeled versions, as this is merely a change in the cs-file * Easy to give directions to a fellow worker, on which versions we have are currently using * Very easy to check what revision and/or rule (e.g. label) a file/folder is loaded with * One installation gives you all tools you need, Browser, Context support, Label browser, etc. etc. * Easy to check which versions another users is actually using, since we can see other users cs-files. Con's clearcase * Slooooow, at least compared to SVN. (pretty close to a Near Death Experience, as I think of it ) * It is slow both in the CC-browser and in the Windows environment. * Costs a lots of money for a license * If you have several projects loaded in a Snapshot view, they will all use the same version of linked modules. * if network goes down, and you are working in a snapshot view, you might have trouble just browsing the folders (depends on your settings) Pro's SVN * Fast * Very light weight * Easy to introduce to customers * Easy to learn * Good interface (Tortoise SVN) * Easy to setup a simple repository * Different projects in a working copy, can use different versions of the same module (specified in svn:externals) Con's SVN * There is not one tool that gives you all the functionality that you get from ClearCase * Depends a lot on that rules are followed by the users, unless you create server hooks to check user actions (but that is not in the base install), E.g. tagging/Branching is merely copies, so it is up to the user to select where a specific tag is stored. If a user accidentally stores a Tagged version in the wrong place, others might having a hard time finding it. * Not as easy as CC to find what tag a specific file belongs to, since this has to be determined from the path * Linked modules are linked with absolute paths :headbang: , which means that it is not just to move a repository from one server to another (as all svn:externals must be fixed) * You'll have to install a few software packages, at least if you need the CLI support as well as the support from TSVN * Doesn't handle renames as well as ClearCase, a rename in SVN is a delete-add operation, which means that revision history is lost (I might be wrong on this)
  25. QUOTE (crelf @ Sep 25 2008, 05:43 PM) This was really neat, thanks! :worship: /J
×
×
  • Create New...

Important Information

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