LUDICROUS ways to Fix Broken LabVIEW Code with Darren Nattinger | GDevConNA 2022

แชร์
ฝัง
  • เผยแพร่เมื่อ 13 ธ.ค. 2024

ความคิดเห็น • 7

  • @petrutarabuta5617
    @petrutarabuta5617 2 ปีที่แล้ว +2

    Thanks for pushing for higher LabVIEW editor and run-time stability. Around two years ago I too was bitten by an issue whereby my LabVIEW 2018 application wouldn't build into an EXE anymore after using my own custom-made malleable VIs deeply nested as subVIs inside other lvlib-owned VIs. The code worked perfectly fine in development environment. There were no broken run arrows. For a while I played tickbox roulette exactly as you described. In the end I refactored the malleable VIs into regular VIs. This worked, but it led to code duplication in the sense that for each malleable VI I had to create two or more regular VIs that were virtually identical, but were adapted to a particular data type. The whole investigation and refactoring cost around a week of work.

  • @bajvisajahl1726
    @bajvisajahl1726 2 ปีที่แล้ว +2

    This Man is a legend

  • @antoinechalons
    @antoinechalons 2 ปีที่แล้ว +3

    i use lots of nested malleable VIs with classes that have an inheritance tree with more than 10 levels
    works fine on Win / Linux / RT Linux

  • @chudchadanstud
    @chudchadanstud 2 ปีที่แล้ว +3

    1) Call NI and tell them to do better. They should try building NI MAX using LabVIEW. They'll know everything that's wrong with LV.

  • @meisuci4708
    @meisuci4708 4 หลายเดือนก่อน

    I jave message LabVIEW: (Hex 0x4A) Memory or data structure corrupt. How to solve it?

  • @beest_
    @beest_ ปีที่แล้ว +1

    What a disheartening demo. NI please get your priorities straight. NXG sucked so much resources, giving everyone else these bugs