Jump to content

Axelwlt

Members
  • Posts

    16
  • Joined

  • Last visited

Posts posted by Axelwlt

  1. The swap value does not seem to get rid of the problem. The second data instance is still in memory. (When I call the VI several times in a row the number copies grows less with the swap, but that's still not good enough.)

    If I use the Request Deallocation VI, that seems to get rid of the copies when the VI finishes, but I don't know if that's a good design. And the second copy is anyway in the memory during that the VI runs, which I would prefer to avoid.

    I already looked at the TDMS with external DVR but I don't know if/how I can use that. I don't seem to be allowed to wire a normal  DVR to the VI.

  2. Hi

    I am reading big TDMS files (~1GB) and I try to minimize memory usage.

    I read a signal once and I want to keep it for later usage, so I tried to write it to a DVR in the hope that I have only one instance of the data in memory.

    image.png.c141382bf34f0f62efa1c654500f6b31.png

    However the task manager tells me that uses 2 times more memory than it should.

    I think the problem is that the array is not deallocated although I don't need it after writing it to the DVR.

    Is there a solution to make sure I don't have copies of data?

  3. Thank you François, that's a nice library!

    Would it be possible to also get the event types from the TD (User Event/Mouse Up/...)? I don't find where this data is located in the TD.

    Ideally the event type should be a "vi.lib\event_ctls.llb\lveventtype.ctl" (so that it matches with the EventStructure:Get Handled Event method), but I don't know if the values match . In the enum, User Event is x41, but there is no x41 at all in the TD.

  4. Hi

    I would like to add some more information to the Actor Framework's Message Enqueuer class, so I thought about inheriting from it, with some additional members.

    However, the issue is that the only way to get the Message Enqueuer of an actor is with Read Self Enqueuer.vi, which returns a Message Enqueuer.lvclass.
    And I don't find any way to transform this value into my child enqueuer class.
    Message Enqueuer.lvclass does not have data accessors to let me copy its internal data, and I can't modify Message Enqueuer.lvclass.

    Is what I would like to achieve impossible?

  5. Hi

    My main VI contains a whole bunch of splitters and inserted VIs. These VIs all need to react to Pane Size event of their pane.

    The event comes as expected when the user resizes the main window. But it does not come when I programatically set the main FP Panel Bounds or Windows Bounds.

    How can I force the event to come? Programatically moving the splitters 1 pixel and back does the trick, but that's an ugly solution.

  6. Hi,

    In a Mouse Down? on a tree, I need to know if the user clicked on a expand/contract symbol, because I need to discard clicking on items but I still need the expand/contract mechanism.
    I would need something similar to the InSymbol from the Point To Row Column method, but for the expand/contract symbol.

    How can I do that?

  7. 5 hours ago, JKSH said:

    You could keep the .ctl as a Type Def most of the time. When you want to propagate cosmetic changes during development, temporarily Save + Apply it as a Strict Type Def. After that, change it back to a Type Def.

    That is what I am currently doing but I wanted to speed up a bit this process.

     

    32 minutes ago, Chris_Collier said:

    You could write a script which runs during build which sets the strict type-def to a standard type-def, then reverts to strict after the build.

    How can I do this change? I guess that would be something belonging to VI Scripting?

  8. Hi,

    Is there a way to make a type def behave as a Strict Type Def during development (so that cosmetic changes made to the .ctl are propagated), and as a Type Def. at runtime (so that the cosmetics can be still be changed with property nodes)?

    My use case is that the code just needs to colour the controls at runtime, the other property values are decided during development.

×
×
  • Create New...

Important Information

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