Jump to content

Antoine Chalons

Members
  • Posts

    955
  • Joined

  • Last visited

  • Days Won

    34

Posts posted by Antoine Chalons

  1. Strange, I have no problems with saving VIs created that way. I have never dive deep into context related issues. I remember that there were some problems with RCF's context.

    Any suggestions what should I wire to Application input of "New VI" block? Now there is a This Application constant.

    Hmmm... this is weird indeed, I have only tried in LV 8.6 and I can't save the new sandbox VI...

    I think the best way is to use the "main application context" because my experience is that working into other "hidden" context creates problems (like the VI is not runable but you can't have the error list, etc...) I'm not sure what's the best way to get this context's ref though...

    Here's my first sandbox plugin "Horizontal align and distribute nodes" (saved in LV 8.6) it's quick and dirty but I'm happy with it and it took me about 10 minutes to make it... If I had tried to make a proper RCF for that I would have given up before the end.

    And this is why the scripting sandbox is really cool! great job :thumbup1:

    Horizontal align and distribute.vi

  2. I wonder who clicked green "+" without even downloading the code... (download counter is still 0).

    Anyway, whoever did it, thank you :)

    It maybe because the person first downloaded it from NI community and then rated it here on LAVA... just a wild guess ;)

    The RCF Plugin is really cool vugie!

    One thing that bugs me a little though is that when I create a new plugin by using the context menu option "New Sandbox VI" the VI generated is in the JKI.LV.Extentions context and therefore not savable... wouldn't it be easier to place the new plugin in the main application context?

    I guess it is possible to choose the context in which you create a VI, but I was wandering how do you create your own context programmatically?

  3. Did you manage to compile SQLite for the Mac?

    I managed to compile sqlite on a virtual machine, but whatever I tried, labview always said it was an invalid library.wacko.gif Even the Mac library I downloaded from the sqlite site wouldn't load into labview.angry.gif I think it probably has something to do with the "bitness",

    Any Mac gurus out there?

    I suggest you create a thread in the mac section to discuss this issue.

    On a side note, I think there are some mac maniacs on info-LabVIEW, dunno if you use it...

  4. I think the problem is one of visibility, not enthusiasm.

    I think this is a great idea, I do visit the idea exchange on a regular basis (once or twice a week) and when you go there you automatically arrive on the "hot ideas" and the "new ideas" button is quite small, so even going there regularly I miss some ideas I would have voted for.

    Publishing ideas by block every few weeks would make it easier for voters to follow, I think.

  5. I am not proffessional in labview but trying to make an educational program. I have leaarned a lot so far from you guys in this forum.

    My new problem is that i have a Tab control which has differnet data in different numeric indicators. I have also 2 buttons. I want to set them as whenever i push any of these buttons, the default values in tab control changes. Could help me in that regard?

    Hi,

    You can't use a property node to write the default value of a control if the VI in which that control is is running, you will always get the error 1073 coming from the property node (the description is : "This property is writable only when the VI is in edit mode, or this method is available only when the VI is in edit mode.").

    That means that a VI can set the default value on controls of another VI only if the target VI in not running and in edit mode (not in exe).

    To do what you are describing you should probably concider using a config file.

    Hope this helps

  6. Hello,

    I would like to build an installer for my compiled LabVIEW 2010 application. The installer will be run from an network directory and I would like the installer to log some information about each installation. I would like to capture user name, computer name and date to a text file or database to facilitate any future support / update notifications.

    Is it possible to extend the installer with this capability?

    Thank you,

    Peter Laskey

    You can create a small separate executable form the main one and get the installer to run this exe after installation.

    This "post install" exe can capture whatever you like to a text file.

    Hope this helps

  7. Hi all,

    How to make sure that the "you need to restart your computer to finish the install" dialog will show up at the end of the installer?

    As I understand it, this dialog will show up or not depending on which components the installer had to install, and if it just has to copy my small exe, then it won't show up.

    I'm running 8.6 - I'm saying this in case in the newer versions, the option "ask/force reboot after installed" appeared.

    The only way I could find for now is to create a small other exe in the project, and that small exe is launched after the installer finishes ; all it does is show a dialog to ask the user to reboot.

    Is there a better way to do that?

  8. It's curious that you mention 8.6's stability. By the CAR count, 2009 was more stable than 8.6. But these sorts of things are subjective to the parts of LabVIEW that affect you daily, so different customers may have experiences that vary greatly from the objective count.

    Really true.

    And when someone's happy with one version, there has to be some good reasons in terms of feature to move to a newer version, not just the fun to have the latest version.

    In case you haven't heard, LV 2011 is going to be largely a stability release. The entire LV team, acting on requests from customers, is going to pull back on features, focusing on bugs, performance and integration between existing features. There will be very little that is new in LV 2011, but we think customers will want it nonetheless.

    That's a great piece of news!

×
×
  • Create New...

Important Information

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