PiDi

Quick idea from the voice in the back of my head: Defer Panel Updates before the initialization steps, then enable it before inserting plugins. Maybe it will force LV to redraw the panel.

Alt + Print Screen captures only current active window, not the entire screen. You'd only need to make your app window active before this, but this can also be achieved through API calls.

I'm using ViBox probles from SAPHIR (they're on VIPM), and all of them are xcontrols. I've never noticed any fatal crash on windows. And, of course, they doesn't work on RT.

I once asked similar question on the other side, with excellent response from AQ: http://forums.ni.com/t5/LabVIEW/LVOOP-Objects-sizes/m-p/2134884. It's been almost two years (whoa! really!? two years!? O_o) since then, so some kind of update might be necessary (as AQ stated there: "The compiler and its optimization systems were massively different in 2009, slightly different in 2010, somewhat different in 2011, and should be vastly different in 2013"). As for my experience, also from the application I was talking about then: I haven't ever reached the point where I must make optimizations specifically because LVOOP is wasting too much memory. The DVR in class private data is a way to go if you want to constrain data allocations, but this is not OOP-specific, you'd do the same if you use simple clusters.

Shot in the dark: try setting WebServer.Active property to false before setting port, then activate it again. Maybe it will restart with new configuration.

Strangely, if you put "help@@google.com" into item name, you get "help(@)google.com" in menu. That's as far as I got. Ed. Aaaand I found it: put underscore before @ in item name and you're good: "help_@google.com"

That's very suprising to me. I took CLED exam two weeks ago.. And probably failed miserably However, I have a strong feeling that if I were more used to example projects, I'd do much better. The exam I got was very similar to the example projects and I some of the functionalities needed to pass exam are already implemented in those examples. My main mistake was choosing wrong template and loosing time to adapt it into my project. If I'd just choose right template and use it as a starting point, I think there would be no reasons to worry for me now.

At first this might seem as odd behaviour, but if you think of it - it is just as event structures work. They queue events to be handled whenever the structure is called, and this queue is made when the VI containing evstr enters running state. Now, if you close this VI before all the events are handled, there would be some leftovers in the events queue (that's also one reason why we should unregister dynamic events when leaving VI with evstr). You can easily see this in Event Inspector Window (very neat tool in 2013 by the way). And that would be something I'd expect - if I'd treat event structure as simple FIFO, I wouldn't want it to lose any data I put into it, so I expect to get next event the next time I call this particular structure. Of course, only if this VI would never leave memory during the application run - I strongly believe that making dynamic calls to this VI and closing its reference afterwards would also clear the events queue (easy to check, I just don't have time for it right now). For more fun: If you make this VI preallocated clone reentrant, you can be sure that there is new events queue for each clone. If you'd make it shared clone, you might, or might not, come across one that already has something waiting to be handled. However, I can see other issue there, and that is the order of events. I've seen many strange cases where order of events were just not as I would expect it - i.e. the value change of one control called after, not before, mouse down event on other control (this is kind of unfixable issue in one of my applications). This is one of those cases, I think the right order should be value change on focused control first, and then value change on the one with key binding.

Have I experienced this? - Yes, I'm experiencing it all the time. Break single dynamic dispatch VI in large hierarchy of classes, and you'll see never-ending list of errors. Try to fix this VI with this list open, you'll experience never-ending updates on the error list. I find it especially annoying when using quick drop. For some reason, when you have error list open and use ctrl+space, the list would be refreshed again, and again, and again... before actually opening the quick drop window. And then the same when you'd try to make any operation, like removing piece of code. The only workaround I have so far is good hardware (I think SSD is the key factor here). It is possible that disconnecting compiled code from VIs helps, but I don't have enough evidence for that (I've just started to use this option together with a new computer, so I'm not sure if disconnecting code actually helps in this case).

cross-post: http://forums.ni.com/t5/LabVIEW/Application-builder-error-1055/td-p/2759902 Hello everyone I have a big problem with building applications lately. The build is running fine until the end, when it throws: Error 1055 occurred at Property Node in VISL_findDependentVISvr.vi->VISL_findAndProcessVISvrList.vi->VISL_detectAndCopyVISvr.vi->AB_Engine_Copy_CustomIOServer_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller Possible reason(s): LabVIEW: Object reference is invalid. Has anyone seen this error in app builder? Does anyone have any idea how can I resolve this problem?