Jump to content

jgcode

LabVIEW Tools Network
  • Posts

    2,397
  • Joined

  • Last visited

  • Days Won

    66

Everything posted by jgcode

  1. [cross posted to ni.com] Is this related to how the new plots are implemented in 2009? Are the FP Objects here, associated with a default class (or in this case an array of classes)? Or is this totally different?
  2. Hi Levin {by control pane I am assuming you mean functions palette) If the drivers did not come with a palette file you make your own. I recommended sticking the driver folder under the LabVIEW hierarchy e.g. <user.lib> (or where ever) and create a palette menu for them by selecting Tools>>Advanced>>Edit Palette Set from the LabVIEW menu. Alternatively you could use VIPM. Cheers
  3. This was very cool. But I am of the understanding that it was a sneak peek not a 2009 feature - is that correct?
  4. Hi Adam I was under the impression that just the files that have name collisions are remapped to folders inside the exe. But from your post and rereading the help documentation, it seems the entire exe structure is mapped as the development environment folder hierarchy. Is this correct? Where do vi.lib, user.lib files outside the (top level) src directory go? Cheers Time for some playing!!
  5. I wanted to post about how impressively fast I thought 2009 was compared to 8.6.1 but I didn't have all the module installed at the time and thought it might be due do that. But yes, I have noticed that it is quick to start, even with all the palettes loading on startup, RCF, etc...
  6. Hi Eugen You will be pleased to know, as I am, that is has been Check out the release notes or I posted details here
  7. Looks good It has taken a while to adjust to the toolbar on the RHS.
  8. I must clarify annoying - one of the features I like about VIPM is its ability to install and uninstall packages, upgrade versions etc.. All this is quite transparent to the developer. If I have to manually handle this, then yes, I see it as annoying. As for quickly solving my problem, I cut and pasted the icons in the directory before I started the topic I just want a clean way to do it Anyways thank you very much for replying and the snippet. I am trying to post to Ideas Exchange about the public folders. But it is coming up with Post Flooding - wait 900 seconds By the way - its seems you have posted some interesting Ideas on LVOOP - good job PJM just made a cool post editing the Icon Editor! Maybe I could give that a go!
  9. Hi John, welcome to LAVA. If the screens need to interact with each other then I would go a different route - but from what you are describing with the modal screens - the user can only use one screen at a time so the following may work for your application: Would using a main screen containing a subpanel with a common toolbar and run time menu sound like it may suit your GUI? Similar to what you would find withe LabVIEW Options dialog. I like using this for most of my applications that have multiple screens and can share common buttons/menu items. Cheers JG
  10. [cross posted to ni] Is the sequence structure package shown in the video available to download anywhere? I would love to use that for a current project.
  11. Hi Sydney You could try using the above FP Method to print only the visible front panel objects. You should have the same or similar node in 8.5. You may also like to check out the Report Generation Toolkit (RGT) if you have it. I also like to make the dummy VI as Ton suggested. Cheers JG
  12. Thanks for posting. I tried editting the SPEC file but that failed. Typing in the symbolic path fails - it must do a check - it just changed it automatically to something else. I have not looked at the post install scripts (I actually didn't know they are there - only the post package build scripts - e.g. hooks build into VIPM). I can easily get the default directory from a LabVIEW primitive. But it will be annoying as I would prefer VIPM to handle the installing/uninstalling of files. <edit> Just tried the following: The <temp> is not always a subset of default data in VISTA. E.g. my <temp> is C:\Users\ME\AppData\Local\Temp by my <osdatadir> is D:\ME\Documents\LabVIEW Data. This is because I changed mine so that my data is not tied up in the OS volume. Bugger! </edit>
  13. We should be able to get Windows 7 RTM through our MSDN subscription soon (if not now) - I would like to look at upgrading so that's good to hear. Damn work PCs Intel chips don't support virtualisation, will have to push the boss for an upgrade
  14. If a design is used for a SM with state information stored in cluster - but with the cluster being made up solely of (e.g. LVOOP) objects (so the cluster is only used as a container to pass the objects through the states to avoid multiple SR) - would that still be considered bad design? Note: I ask out of an effort to seek information, not to debate any previous comments.
  15. Just out of interest - the VI snippet does not include the Tagged Test VI.vi - which is the VI being statically referenced. Do people think it should or would be a good idea if it did?
  16. As far as I know (and please correct me if I am wrong - I just remember someone else posting it) the OpenG forums are quite inactive so I thought I would post here Hi! I currently host my icons templates in the palette, this way I can quickly drag and drop them onto the FP then into the icon. This was a pretty fast way to do it for me. Now with 2009 I want to create a package that can install these to <osdatadir>\Icon Templates\[my folder structure etc...] However, it seems that OGPB does not support this symbolic path? So my question are: Does OGPB support the <osdatadir> symbolic path? Is there a better way to do this? Cheers JG
  17. Cool post. I loved the bit where they jumped in and were hitting the screen with shovels.
  18. This is the way I normally do it. Thought I would mention that Sciware likes to do it this way with the advantage being you will know straight away if the dynamic VI is broken - this way makes a lot of sense.
×
×
  • Create New...

Important Information

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