Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation


About osvaldo

  • Rank
    More Active
  • Birthday 01/16/1971

Profile Information

  • Gender
  • Location

LabVIEW Information

  • Version
    LabVIEW 2015
  • Since

Contact Methods

  1. Thanks for the reply Hmm ... Yes ... In fact it would seem that way ... would require that only the class can instantiate DVR relative to a subclass B derivative of it. The only pattern that comes to mind is the abstract factory, but not I see a use case that requires the option in question ... On the Internet I found no example where this approach was used. Maybe I'll understand the meaning if I happen a situation that makes clear the need for this setting. At the moment I'm just studying the object model of LabVIEW trying to bring him back to what we already know. Thank you Osvaldo
  2. Goodmorning everyone! We program in LabVIEW for a long time (fifteen years), but only recently have I been able to devote to learning OOP techniques with LabVIEW. I state that I have little experience in general with the OOP having in fact only a theoretical knowledge of the concepts and patterns and few experiments made in Pascal ... (eh ... eh ... ) I come to you humbly ask for the meaning and use cases of the "Restrict references of descendant class type to member VIs of this class." In the tab on inheritance I could not connect this option with any of OOP concepts known to me. Thanks
  3. I do not know ... During the process of packaging, VIPM freezes and I have to stop killing the process ... Curiously, however, remains open window of the VI OpenG Builder ...
  4. Thanks jgcode... I have cross-posted even there, but I thought that perhaps some of you might have encountered the same problem ... However, I will follow your advice and try again even on the forums .. JKI Have a nice day Osvlado
  5. No one have experienced the same issue? No idea on how to fix this problem or where it can be located in the OpenG Builder code? Thanks. Osvaldo
  6. (cross-posted in http://forums.jki.net/topic/1324-recursive-vis-cannot-be-built-in-package/page__gopid__4548#entry4548) Hello to all, boys, I'm using VIPM ver 2011.0.1 (build 1692) dic 07/2011 Community Edition with OpenG Builder ver 3.0.1-2. I am trying to create a package to a library for LabVIEW 2011 that uses recursion native, but Package Builder gives me the same problem described by Kring to "Known Issue (Case 8006): VI Package build hangs in LabVIEW 2009 when recursive VIs included in package" and stated fixed from version 3.0 and later ... I think in my case the problem is that rec
  7. Ok! Thankyou! I use it like tag variables... I'm writing a library based on the idea of the NI CVT reference Library where the inner data storage based on Arrays where replaced on a number of dinamically created notifiers, one for each tag defined... My hope is that each reading/writing operation on notifiers is decoupled by each other, so that different loop can run in parallel so much as possible (the implementation of the original CVT reference library serialize all access on the AE that encapsulate the assary it self...) Ok... Ok... I could used the Shared Variables, but when the
  8. Hi Very interesting! So... speaking to the guy who writed the primitives... what about the Notifiers Primitives? I usually use them to send signal (like booleans to quits parallel While loops, o to send chuncks of data asynchronously to many consumers), but now I'm working on an library that will use them to broadcast data to parallel tasks (using named notifiers)... Any issues? On realtime targets? Thanks Bye! Osvaldo
  9. happy to be of help! Osvaldo p.s. where you came from?
  10. Hi mandya14, Sorry for bad English ... but not my mother tongue ... Let me understand... I guess you a while loop containing a VI (from your device driver toolkit) that returns the status of DIO and you set the value of this DIO directly into a boolean indicator through its terminal. On the other hand you have another while loop that contains an event structure with which you collect the event "value change" on the indicator whose value is set from the di DIO... I understand you correctly? If it is correct, your problem is that setting the value of an indicator in this way *does not* tri
  11. Hi mandya14, i think that is impossible for an indicator to send an event at an event structure... Even in my last project a find that a numeric double indicator does not trigger any value change event... In my application the event would be sent when the I/O loop change the value via the Value (trigger) property... Even a control with the Disable property set to 1 or 2 is not able to trigger events! To solve the problem, i change the indicator with a control and than I put an rectangular trasparent decoration to mask the control itself... Or make a tiny loop that trigger the event whenev
  12. Oh! This is an idea! I never thought of! Thanks! Osvaldo
  13. Thanks! Can you retrieve the Type Descriptor of these OLE Variant Types using the Variant To Flattened String function? I would like to directly convert a variant array in a given cluster type, as with the original LabView Variant to Data function do. I was unable to convert the array into a cluster directly using the Database Toolkit palette version function... it seems not to handle the aggregate types ... If it were possible to get the type with the type descriptor, I could dismantle the array and rebuild the cluster using the same technique used in OpenG toolkit ... Osvaldo
  14. Hi to all, I'm writing an application that use an MS Access database to store test report data... The queries to the database tables and colums are made using the NI Database toolkit. This library returns the data into 2D array of variants, so i've made a VI that try to convert this array (line by line aka record by record) into an 1D array of clusters representing one record each. To do this I'm using the "Variant to Data" node, passing the 1D array of variants as input and specifing the cluster as target type... Well... If I create the 1D array of variants assembling data from control
  • Create New...

Important Information

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