Leaderboard

Not all of my answers are useful..... Splash screen going black? Haven't seen this. Locked classes? I bet there IS something running in the background somewhere or a reference to a sub-VI left dangling.... The installer configuration will actually do a "Preview" of all executables before opening the dialog. The time taken is therefore basically equal to the amount of time taken to do a preview of all of the other builds included within. Extremely annoying. VI outside a project: Context. The VI saves information regarding to the context in which it was opened. Same problem occurs with RT and Windows and FPGA, my VIs I reuse on multiple targets demand repeated saving event hough the code itself has NOT changed. This kind of bookkeeping rubbish makes life hard when working across multiple targets (And project and not project are two different targets) compile cache leading to saves? I don't know. I haven't directly observed this. (maybe liked to context changes between the version saved on disk and the version in memory?) Cursor not tracking properly? Graphics driver. Windows 2D graphics acceleration. Virtual machine. Take your pick. Saving VIs after a build.... I think the build opens the VIs in a different context for compiling and if the VI contains any target-specific code, this will be saved as part of the annoying constant bookkeeping LabVIEW does with its binary files which are "suppposedly" separated from source code. Why the last context needs to be saved in a VI I do not know, but it's something NI is holding on to in future if you get my point. VI not being edited wanting to be saved? Don't know. Again, possible context differences between disk and memory versions of VI. Every VI in memory when opening a project? Because that's how NI decided it should be done. Search system. There's nothing to explain here, so I claim this point towards my beer tally by default. Cancelling a build. This is a PITA and I have no explanation beyond sloppy implementation. Finding all instances of VIs with different search windoes : Never noticed that. Must watch out for it in future. EXE icon, again nothing really to explain here. Crash when undoing QD. QD is buggy or is using unstable methods. We've had several cases of QD shortcuts creating corrupt control references which ended up costing us days of debugging to find. Random crashes and general instability ensued. Accessor creation. Because if working with Classes would be too easy, the sense of achievement when actually managing to get the code working would be severely dimished. It's for the best. Class prioperties dialog. No idea and it always annoys me too. SCC login. Haven't used that for years after downloading a free version of Perforce. Here again, nothing really to explain. Beer counter = Beer counter + 1 last two dealing with bew services. Don't use them, no comments. To add to this list: When deploying code to a RT target, we're never quite sure which version of code gets deployed. Inlined VIs, when saved with changes, do not seem to propagate the "changed" flags to their owning VIs which then leads us to do a bottom to top forced recompile in order to properly re-sync the compiled cache with the code. Even then we sometimes get VIs marked as running on the RT which shouldn't (have just been removed) or vise versa where a VI which definitely IS running on the RT is not marked as running int he IDE. Frustrating as hell and a real time waster. FPGA compiles continuously reporting that the maximum number of messages from the compile server have been exceeded and there'll be no more feedback on the compile process until the compile is finished and even then half of the timings and resource utilisation statistics are missing...... I LOVE having to wait 2.5 hours for no useful information. Window juggling in the IDE. I want to open a VI and go straight to the block diagram. Double-click, Ctrl-E in short succession. Window swapping ensues and after the graphical random number generator is finished, my Ctrl-E nearly always gets sent to the project window which then switches to files view. 30 seconds later I can get back to work. Lovely. I also love how the Internet Toolkit is deprecated but there is no VI in any current toolkit (that we have found) to parse a CGI string. Icon editor has, since several versions, not been able to connect to NIs server to update the glyphs. Also, the glyphs are seriously lacking, far too few standard LV glyphs are included. I also love that the project does not allow two RT targets to share the same IP address. We have one host software with several versions of our RT system, only one of which is ever connected. If I give two targets IP addresses of 10.0.0.15, LV cries. If I give one 10.000.000.15 and the other 10.0.0.15, labVIEW is quite hapy (And apparently, stupid). Shane

Looking forward to another NI Week and Lava G BBQ. Thanks a bunch David for posting on the other thread. I had given up after seeing no new messages by the end of June.