Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/31/2014 in all areas

  1. I have written a paper on the Strategy Pattern (with appendices on Interfaces and the Factory Method Pattern) in the hope that this will be a useful guide to others. We have published a PDF version of the paper: StrategyPatternWithLabVIEW and a zip file that also includes the source and model: StrategyPatternWithLabVIEW--WithModelAndSource. You can comment on the paper here, if you like. Paul
    1 point
  2. G Systems is giving away a Raspberry Pi complete starter kit with everything you need to create a streaming media player. Happy tinkering.
    1 point
  3. Hey All! Enable Integration (www.EnableIntegration.com) will be there too, we're thrilled to donate the following door prize: We will be using the opportunity to exclaim that we're hiring, and shamelessly try to recruit you to come work in Toronto. (Yes, I mean you!) PARROT AR.DRONE 2.0 *** ELITE EDITION *** Remote control quadricopter controlled using an iOS or Android smartphone or tablet 720p high-definition live video streaming & recording to smartphone or tablet while flying Record & share videos & pictures straight from AR. FreeFlight piloting app
    1 point
  4. But seriously when I had this issue, the easiest solution was to checkout the project to the shortest path I could. Since then I check out my code to C:\SVN\Project Name. VIPM also had issues in the past because it would build packages in a directory along side the source but I think they now build in a temp folder for this reason. EDIT: Oh and as for builds we do put the EXE in source code control but not the installers. The reason for this is because if I build a LabVIEW EXE, then build it again with the same source code, the EXE's won't be the same bit for bit. They may function the same but there is no way to know for sure that the 1.0 EXE is the same functionality as another 1.0 EXE. So if we needed to make a new 1.0 EXE by rolling the source back, then rebuilding we wouldn't know it is the same as the 1.0 made previously. I don't really like that some builds are in source but it makes life much easier when I need to roll back and try a previous EXE.
    1 point
  5. Jack and Michael, if you are "listening", I think this kind of stuff would make a great topic for VI Shots live.
    1 point
  6. Sixclear believes in being sexy. In the promotion of this principle, we are giving away a new FitBit One: I tried to paste the largest image available. I believe I've succeeded. See you next week!
    1 point
  7. A few interesting points: The mobile app will not allow you to add personal events (meetings, LAVA BBQ, Etc) but the full web version will. The full web version will not allow you to schedule more than one event at the same time but the mobile one will. The full web version will not allow you to schedule a personal event that takes up part of another event (like one that runs into lunch). Kinda annoying overall. As for the sessions, I have been able to book up most of Tues and Weds but on Thurs I have at least 3 sessions at each time slot I want to attend. Why do they do this every year? For each track, they should spread the sessions in the intermediate and advanced categories out so there is as little overlap as possible!
    1 point
  8. I have no insight as to what would or would not kill the web guys.
    1 point
  9. thanks! would it kill the web guys to put that on the main page somewhere? I just accidentally discovered I can get to it by attempting to re-register. not very intuitive...
    1 point
  10. Through the regular web interface, you can use the Export button. I was able to successfully export to my Google calendar with this option:
    1 point
  11. Since it currently looks like I won't be there on Thursday, go for Fab's presentation on Unit Testing.
    1 point
×
×
  • Create New...

Important Information

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