Jump to content

jgcode

LabVIEW Tools Network
  • Posts

    2,397
  • Joined

  • Last visited

  • Days Won

    66

Posts posted by jgcode

  1. If I were to want to place a single typdef'd cluster on one of the pages, but write just the individual items from the cluster to the ini file all under the same section, is there an easy way to accomplish this? I want to maintain my typedef and not break things apart on the page, but it currently writes the entire control into the section which makes it difficult to use the OpenG read INI or Section Cluster VI's (though perhaps I'm missing something). I've looked at your example readfromdisk.vi, but it's pretty much what I've already tried. The workaround is to place the cluster into another cluster when reading and then pull the desired cluster back out and that makes me cringe.

    I guess that's a side-effect you are getting from mixing your data and view (which LabVIEW makes it easy to do).

    Wrapping your typedef in a cluster is the correct approach and is how the framework works.

    It will allow for scalability if you want to add elements (that may not belong in the typedef in the future) to your page (or section).

    Not sure if there is any other way but pls post if you come up with anything cool.

    Cheers

    -JG

  2. I have sent Objects using TCP/IP or Shared Variables and it works fine.

    Making the network comms transparent to the local messaging framework via some proxy makes sense.

    Given your preference - if AMC has TCP/IP support built in (?) then you may be able to combine it with Lapdog to achieve the functionality you are after.

    Additionally it may be worth looking at LVx etc... - as all this stuff may already be done for you :)

    Paul posts a lot about this architecture (LVOOP over TCP/IP) I would check out this previous posts too - it may help.

    Cheers

    -JG

  3. LabVIEW Champion Jeff Bohrer (featured here and here) aka the Spinning 8-Ball will be donating the BBQ's second mystery prize...

    Whilst Jeff cannot attend in person, the wonderful Fab will be bringing the gift.

    What will it be? Who knows (I don't)

    Come along to find out :thumbup1:

    index.php?app=core&module=attach&section=attach&attach_rel_module=post&attach_id=467

    Showering us with further gifts, Jeff imparts some wisdom for the LAVA masses before leaving:

    All shall be well and all shall be well and all manner of things shall be well" -Julian

    • Like 1
  4. Preference Page:

    General model (no password): "LabVIEW 2011\resource\dialog\PreferencesDialog\PreferencePages\pageTemplate.vit"

    Example (no password): "LabVIEW 2011\resource\dialog\PreferencesDialog\PreferencePages\prefPage_NISearch.vi"

    Hi lordexod, I am not sure what your post is referring to?

    Can you go into detail.

    Cheers

  5. Thanks everyone.

    I have been told by the obstetrician that they are identical!

    Although I am not 100% sure what he based that finding on (I would have thought DNA would be the only test 100% conclusive).

    Anyways,

    Congrats. Thought you seemed busy. I have a 5-week old daughter myself. Katy.

    Congrats too! Looks like May was a popular month :lol:

    I've never heard of the name "Digby." Is it unique to Australia, a nickname, or did you make it up?

    I am not one to follow trends, but I don't think it's unique - I have heard it before once or twice - but no, I didn't make it up :lol:

  6. distek_logo.gif

    A big thanks to Ed Dickens from DISTek Integration, Inc for the following 2012 LAVA/OpenG NIWeek BBQ door prize:

    41RsZgv7t9L._SL500_AA300_.jpg

    This Bluetooth handheld keyboard is a great accessory for your iPad, iPhone 4 (or later), smartphone with Bluetooth HID profile, laptop, home PC, Playstation or Wii gaming system.

    It is a perfect combination of keyboard, touch and laser pointer for teaching or training, with keyboard, mouse and laser pointer all in one hand.

    Features:

    Portable and elegant

    The world's first Touchpad 90-degree flip design

    Innovative design of the Navigation keys

    Windows Multimedia Control

    Built-in rechargeable lithium-ion battery

    Laser pointer / presentation with remote control

    Real QWERTY full-function mini keyboard

    CARPC: car computer's best wireless solution!

    3-in-1 multimedia wireless keyboard (built-in TouchPad & Laser Pointer)

    Sitting in the sofa or on a bed, you can enjoy wireless control

    Built-in rechargeable Lithium-ion battery and also auto sleep/wake mode

    Backlight: with 26 PCS dazzling LED lights to help when using it in low-light environments

    System Requirements:

    Android OS

    Mac OS

    Linux(Debian-3.1, Redhat-9.0 Ubuntu-8.10 Fedora-7.0 tested)

    Windows (all) with USB port

    iPad, iPhone4

    Samsung Galaxy P1000, and mobile phone (with bluetooth HID profile or driver, supporting bluetooth HID keyboard.)

    • Like 1
  7. logo-delacor.png

    The wonderful Fabiola from Delacor has done it again by getting her hands on a limited edition of the A Software Engineering Approach to LabVIEW.

    This is one of Steve Watt's (one of the authors) last copy that he graciously gave to Fab.

    It is one of the ones that actually came out looking good (as there have been known to have been some publishing issues in the past).

    This text has also be signed by Steve Watts - that's one highly regarded John Hancock.

    Thanks for supporting the LabVIEW Community Fab!

    • Like 1
  8. It's that time of year again. What will the next installment of the LAVA/OpenG BBQ bring? One thing is for sure - door prize galore!

    Past prizes have included (just to name a few): home-made creations, gift-cards, tablets, books, Ipods, LabVIEW goodness, software and even a plane-ride.

    We accept anything - so feel free to be creative! By donating a prize you and your company will receive free advertising in this thread.

    But wait, it doesn't stop there! When your donation is drawn on the night, you may take center stage and embrace fame thrust upon on you by the loving crowd who are anxious to have their ticket drawn from Crelf's stunningly good-looking akubra.

    So what are you waiting for? Check out the cool prizes below (knowing there will be more added to this thread as NIWeek approaches). If you would like to donate (please do, we really appreciate the LAVA-love) feel free to add a prize below or PM me with the details and I'll do it.

    If you haven't already get your 2012 LAVA/OpenG BBQ tickets here!

    • Like 1
  9. JGCode: Have you tried this in LV 2012? Opening and running your example project, it is taking 24 seconds to launch the Preferences Dialog and between 5 and 10 seconds to switch pages within the dialog. No idea why.

    It must be because of this code I wrote :P

    post-10325-0-16318900-1338271452.png

    No seriously, thanks for the info - I was able to easily debug the issue.

    This API was written in 2009 and dynamically calls the <resource> VIs.

    There was a connector pane change to optionsFrame_GetPageReadyNotifier.vi which stopped everything from working.

    This is good as it may provide an opportunity to improve the error handling/logic of the API (although I will be refactoring it when 2012 is released).

    JGCode: I checked the Perforce logs... all changes to the Preferences Dialog in 2012 were in before the first beta, so you should be able to investigate this further on your machine. I have to go now. I may get another chance to look at this later this week, but probably not.

    As a side note - it actually worked in Beta 1 and not Beta 2 so it seems the changes were done for Beta 2.

    Cheers!

    -JG

  10. I started down the road of using this as it allows me to make a much more modern looking configuration engine for a large project. And, I'll be honest when I say that I LOVE reusable code. Makes my life easy!!

    However, have you anticipated the need to populate the front panel controls when you load the pages? I didn't see this implemented, and am wondering if I am just missing something.

    If you had this capability, where the page FP controls could be populated with the last values in the cfg file, it would make this the way to go.

    Thanks,

    Wes

    Hi Wes

    Yes, that use case is handled by and encapsulated in the 'Engine'.

    If you run the examples included with the package you should see it in action.

    Cheers

    -Jon

  11. Or Kickstarter.

    That said, I'm not sure how easy it would be to contract a migration like this - the site's in a pretty bad state, and I think it would take people with a little OpenG knowledge to do it effectively.

    Any interest in using CrowdTilt or similar to raise funds to contract out the migration? I would chip in.

    That is a very kind offer Jack however, as Chris pointed out I am not sure who would do the contract work, and that it should be overseen by the OpenG team.

    One way I can envisage it may work is for community members offering to help (with their time) aka LAVA 1.0 -> LAVA 2.0 restoration.

  12. ...and they can be different even though they are in an Array.

    I revisited this post as someone PM'd me for code.

    When I looked at the code the UI structure I posted is actually a Cluster of Clusters (not an Array of Clusters as I thought when I just posted a screenshot).

    So what I wrote was wrong regarding Arrays, apologies - it looks like you cannot have different Ring Strings[] in an Array.

    The Channels did not need to be dynamic so this was fine as a workaround for this use case.

    Here is how I updated the ring (there was only one ring, so searching by ClassName was fine in this case, but you could do it another way) in each Cluster to display different Strings[].

    Cheers!

    -JG

    post-10325-0-84948700-1333765344_thumb.p

  13. Has anyone ever given any thought to the LAVA community creating one single patch for the LabVIEW development environment? In other words, LabVIEW ships from National Instruments and then after installing LabVIEW, a user would then install the Community Patch... ...Imagine if one of the significant LV users who has a high trust/recognition among the community were to say, "I have created one VI package that installs everything free that I consider valuable to upgrade my LabVIEW experience." That makes it easy for a user to just install one thing and get a set of reviewed improvements all at once.

    Whist this is a great idea in practice, I don't see it working as explained.

    As ShaunR pointed out, every developer's workflow is different - and what code/tools they prefer/require will vary.

    Additionally having a large monolithic installation (one single package) does compromise the advantages of modular releases (see elsewhere for discussion)

    I do however, believe that packages (and the both the LVTN and VIPN) solve the proposed task due to their flexibility

    Some of them are available as packages, but many others are just one-off VIs posted to a forum, like an improved custom probe.

    Of course, it becomes an issue when code is not released as a package (for whatever reasons). This is something I have been trying to work on with the Team LAVA initiative. Firstly, only packages are used as the deliverable. Now instead of focusing on select packages (as proposed, although it makes sense that popular LAVA packages definitely get published), it focuses on quality (and hopefully quantity in the future), which is accomplished through the LAVA-CR and the Compatible with LabVIEW (CwLV) process. All the while it promotes the LAVA community.The more packages the better. Once the code is available on the LVTN (or VIPN in OpenG's case) you can download it and manage it - easily from any PC (with internet connection and VIPM installed) without the need to search the forums etc. Just search VIPM.

    Now, if someone wanted to post their recommended community code/tools, it would be as easy as uploading e.g. a .VIPC file (VIPC's are potentially under review to make them better for this task - see here) which references the LVTN/VIPN packages (or could even include other packages). A user code simply download the VIPC file and patch their LabVIEW installation - IMHO this accomplishes the proposed task. Over time, a user could easily upgrade a package due to the modular installation (something that would be more complex to maintain if it was all just a single release).

    A few packages have already gone through this process for Team LAVA and I actively encourage any community members who are interested to participate in releasing their code through LAVA onto the LVTN :) - or if they have any ideas to make this process better - please post!

×
×
  • Create New...

Important Information

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