Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/18/2010 in all areas

  1. Name: quick create a new vi from template Submitter: Black Pearl Submitted: 14 Aug 2010 File Updated: 03 Jan 2011 Category: *Uncertified* LabVIEW Version: 7.1 License Type: BSD (Most common) Installation: Copy the contents to LabVIEW xxxx/resource/plugins Abstract: Speed up creating new vi's from templates! It's using the 'new vi'-hook to create the new vi from a custom template. A plugin architecture allows to map different templates to the keyboard. For a quick-start, try Ctrl+N followed by 'H' (without releasing the Ctrl key). Detailed Description: When using New -> Blank VI from the Startup Window File -> New VI from the menu of any vi or the Ctrl+N shortcut the lv_new_vi.vi hook is called. Releasing of the Ctrl key (when using the shortcut) uses the Default.vit. The next key-press k creates a new vi from the template [...]/plugins/lv_new_vis/templates/k.vit. This is case insensitve and only works with a..z and SPACE. If no template is found or if an error occures, the default action of LabVIEW (empty vi) is performed (Failsafe). In addition to normal vi templates it supports global vi templates and control templates. Even more customization is possible using special tags on the vi or vit. Use [...]/plugins/lv_new_vis/tools/lv_new_vi__TagEditor to read and set them: isBD_ToFront? bring the block diagram in front instead of the front panel isRunMe? will instead run the vi in the template folder. Use this for wizards, more sophisticated scripting and other dialogs. Examples (V0.9.3: seperate ogp package): Try the following keys to see the different possibilities: f: normal vi, FP at front b: BD at front g: global vi c: control w: wizard h: help You do not need to delete the demo templates, a w.vit will load even with w_example.vit present. Compatibility: Developed in good old 7.1 and tested with 2010. I don't know if it works nicely with the project explorer and did never try to use it with projects, libraries and classes. Planned Features: * Error logging * Redirections via Config file (I will link the standard templates) (Edit: It's faster to just place them in the templates folder.) V 0.9.1 Fixed issues with the Application Instances of LV8.0 and higher. Wizards are still launched in the diaolog App.Instance, they need to get the default App on their own. V 0.9.2 Changes: Closing all references Beta: Uses VI Activation Event to abort when the user switched to a different app. (See discussion for details). V 0.9.3 Uses VI Activation Event to check Ctrl-Key when user switches from a diffrent application. Now available as packages (ogp). Uses a seperate package for the examples. V 0.9.4 Fixed issues with 0.9.3: After start of LV, Ctrl+N didn't work the first time Enjoy, Felix Click here to download this file
    1 point
  2. SysML is the "Systems Modeling Language" -- basically UML for systems engineering. It is implemented as a profile on top of UML. It uses some UML diagrams and adds others. SysML provides a way to model all aspects (e.g., mechanical, electrical, software systems) of a system in a single unified model. SysML provides capabilities to model system requirements, architecture, behavior, and parametrics. It can support simulation for trade studies and so on. You can think of it as CAD for systems engineering. --- We are especially interested in using requirements for requirements management. We are starting to use it in particular for capturing and allocating requirements because it offers the following benefits for that purpose: 1) The most important reason is because we can capture everything in a single model in a (standards-based) tool specifically designed for that purpose. This means that, for instance, if I define a set of common requirements in a package in one project file, I can retrieve the relevant package in another project file. I can add only the relevant requirements to the target diagram. (In a document-centric approach I have to decide whether to duplicate requirements or just reference an entire document. The first option creates a maintenance problem and the latter is very often problematic for the reader.) 2) Each requirement is a unique model element. I can link semantically meaningful items (e.g., <<rationale>>). (These are currently possible in requirements management database tools and you can make this work in a document.) I can create semantically meaningful links (e.g., trace, refine) between requirements. Moreover, I can create links (satisfy) to Test Cases and detail the test procedures, and I can display all of these visually on a diagram. The links help us ensure traceability across the enterprise. Ultimately, this means we have a real chance to maintain the requirements, do real traceability, make sure people actually read them, and consequently, we hope, meet them. --- OMG's page on SysML offers a start (OMG) The best book I have found on SysML (by far) is A Practical Guide to SysML. Paul
    1 point
  3. For reference, these are sung in this fashion Here A girl, once named Joline who had reviewed my queued state machine said “No matter what you put through, Your data never quite fills the queue.” But, I told her six is both average and mean. Aye aye yai yai your program only works w/ 'run continuously' so sing me another verse that's worse than the other verse and waltz me around by my while loop A crowd of chicks from R&D were impressed by my large VI Tree. They’d all hoped for a squeeze but I said, “Ladies please, I must limit my queue size to three.” Aye aye yai yai your error wires have always been funky ..... I once knew a girl from japan who was looking for a block diagram I pressed control E and saw his dependency tree and swam all the way back to San Fran Aye aye yai yai If you like that one head over to 'Kiss & Fly' ...... I once knew a girl from floor three who said she had her eyes on me She liked my VI’s most So I wrote her a blog post and now I can’t keep her followers off of me Aye aye yai yai Christina please forgive me for that one...... I once knew a man from Racine who invented a finite state machine meally or moore, it could't keep score because it didn’t even fit on one screen. Aye aye yai yai nobody likes my block diagram colors ...... I once knew a man from Peru Whose for loops only went to iteration two........ aye aye yai yai If you didn't groan at that you've got issues ...... I once a girl named Alli whose while loop had gone to iteration three and then it stopped.... aye aye yai yai You leave breakpoints in password protected VI ...... I once knew a girl I thought hot Who I saw had a grey coercion dot When I took her to bed The damn thing turned red and I ended up in a memory leakage spot aye aye yai yai If you like that one your a sick M@#$% F@#$()* {slowed down} So sing me no more verse........ thats gotta be the worst verse.... and press my abort execution
    1 point
×
×
  • Create New...

Important Information

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