Jump to content

Antoine Chalons

Members
  • Posts

    980
  • Joined

  • Last visited

  • Days Won

    37

Posts posted by Antoine Chalons

  1. Hey... well... True I went a bit fast and forgot to check if a child already exists before creating it , but really it's not a lot of work.

    Each time, before creating a child item, you just need to check if it already exists. That's what the first bit of code is doing (tree function "check").

    Give it a try and post what you came up with if you still have trouble.

  2. Too slow/too much effort to file a bug.

    The situation I was realizing I need this feature is when you are in 'the flow'. You go through implementing a new feature and you touch/change a SubVI in another 'code modules' to make your new implementation working. In this situation making the SubVI 'clean' would throw me out of 'the flow'. I want just a amazon-one-click-buy-button to mark that SubVI as dirty and go back there later, when the 'big-picture' is implemented.

    But it would not be a bad idea to have an option to sync these statuses with a bug tracker like mantis (e.g. by writing the status in a data-base), as well as to have any status changes in the Changelog of my SCC (maybe as pre-commit hook).

    Felix

    So you could use something like a "tagging" RCF plugins with options like "tag as unclean / buggy / need doc".

    How about something similar to vugie's "Label Manager", you'd have possibility to apply different tags (editable list) and when you launch the manager, it would search the project you are in to find all the tag.

  3. Hi all,

    I just made this little plugin for when I work outside of a project (I know... I should not...) to see where are the subVIs located on my hard drives.

    Here's a video to that shows it on an OpenG VI that I loke a lot.

    <iframe src="http://player.vimeo.com/video/18525699" width="400" height="300" frameborder="0"></iframe><p>

    I can't post it right now because it contains some internal dependencies but I could clean it if someone was interested. anyone?

  4. Thanks, that's what I'm looking for. Seems not to be implemented in 7.1. :(

    I have a style (String) for Node and a Style (numeric) for Scale. But nothing for Constant or Control. Maybe it's available through GetProp.

    Felix

    Haven't checked 7.1, I'm using 8.6.

    I don't think you can get Style ID for a constant... Though if your target is a BD terminal you can get the ref of the corresponding FP control and then get the Style ID.

    I've made a scripting sandbox plugin for that (in LV8.6).

    Show Class & Style.vi

  5. Is there a way to distinguish between Controls of the same Type such as:

    * Round LED, Square LED, Toggle ...

    * String Control of Classic, MOder or System?

    Felix

    At least the style ID property can help. I think I saw more info somewhere but I can't remember where...

    post-7452-0-59066800-1294222898_thumb.jp

    Hope this helps

  6. When working on a project, I normally try to make a feature working first. In this process I leave some VIs in a messy state or apply incomplete bug-fixes on other vi's.

    So I'd like to mark these VI's as 'needs attention', so at a later stage (when ideas arn't bubbling fast or I'm tired) I'd come back.

    This idea is scaling up the more I think, as I'd like to put priorities for 'clean-up' done, and also add other marks like 'reuse candidate' or more specific 'TODOs' like 'make Icon' or 'document'.

    Any standard solutions or should I code my home-brewed tool?

    Home-brewed: I was thinking about a cluster constant which I can quickly set to the desired state when working on the VI and a 'explorer' that allows me to browse a project by the settings of this constant.

    Felix

    That's an interesting topic!

    I made a very simple "focus.vi" a while ago, it has a required enum typedef input with a series of states (urgent, bug, doc, reuse, etc). depending on the state, a pop-up would show up when the VI is executed ; that's how I leave notes for myself into projects.

    That's very basic but it helps me.

    I though about improving it / integrate it into the project so that my colleagues could use it too but talking about it with them I realized that there was quite a lot of work so I gave up and keep using my simple "focus.vi".

    That said, it would be cool if we could have a LAVA discussion on how should that be implemented into LabVIEW and then drop a feature idea on NI forums so that NI Engineers implement it for us ;)

    Cheers

  7. Hello Friends,

    I want to implement a Tree Control with for loop (N=3),

    In my first iteration the tree control should be updated with Tag "Demo"

    Second Iteration: "Demo/Measurement"

    Third Iteration: "Demo/Measurement/Converter"

    Thank you

    I suggest you take a look at the Tree Control API.

    Hope this helps

    • Like 1
  8. I don't understand the auto-tool hate.

    Yep, I have to admit I hated it for a long time and eventually my dad convinced me that it was worth trying, I tried and never turned it off since.

    And now the few of my colleagues who (still) dont' use it get crazy at me when I turn it on on their computers :rolleyes:

  9. hi, guys anyone please give labview mb slave vi.. i need to communicate with PLC master .......

    hello,

    You can get it from NI website here : http://sine.ni.com/d...a/epd/p/id/4756

    I recommend you read the page carefully, specially this part :

    Please note that this is an example program and not an official NI Product. For a more complete, fully supported MODBUS solution, NI recommends the LabVIEW Datalogging and Supervisory Control Module.
  10. I've had such an utility in mind for a long long time.

    Use case : When I start coding a new project, one of my first task is to create all the typedef clusters that will be necessary to store configuration settings, then I create VIs to read/write these "section cluster" from/to INI file (based on OpenG read/write section cluster).

    All this clearly can be automated.

    Using the following list as inspiration sources, I started to develop such an utility as a sandbox plugin. I'm planning to post it here sometime soon.

    Before that I was wandering if anyone thinks this would be useful for them :-o

    Inspiration list :

    • the RCF plugin that creates a typedef cluster from a cluster constant,
    • the create polymorphic VI example from the code repository
    • vugie's scripting sandbox RCF

    PS: I have a video to show what it does know but it's too big to be posted here, I'll find a way to share it very soon.

×
×
  • Create New...

Important Information

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