Neil Pate

Hi there, Can anybody point me to the correct sub-forum on lava to post old NI idea exchange things so they can maybe get more traction? I seem to recall there being a sub-forum called "Orphan ideas" or something like that, but my search-fu has failed me. thanks n

I add a vote to not taking this feature away. Like others have said, I sometimes use a separate Event Structure for User Events that can then be packaged away into a sub-VI.

Would love to have this. I have a medium size project (approx 1000 VIs) that I have to maintain, and edit operations are very slow. Drop VI, wait, make a wire change wait etc etc. I have a similar version of the code base where I managed to fix this by re-organise the hierachy a bit (literally just moved one VI from a library into another, or made it a global variable or something like that), but I cannot seem to make it go away this time around, and do not have time to investigate. The delay is almost certainly due to some type propagation checks or something similar, but I have no idea what the offending code is. If the LabVIEW IDE could just give me some way of letting me know what it is doing when it brielfy locks up I would be very grateful.

Man, I hope I never have to debug any of your code. A class (or VI) name should reflect what it does. I feel it is not really acceptable to compromise on this just because the IDE chokes sometimes when doing these kinds of modifications.

SQL and I have never been best of friends. Perhaps it is time I dusted off my textbooks again!

Interesting query. Is the -- comment valid SQL syntax? Could a badly formed query be throwing the exception?

That thread is from June, I told you my memory was bad I do seem the recall a thead on the darkside discussing fonts and this was where I first learned this tip. Of course I cannot find the thread anymore. Thanks for the reminder though, Anakin.

Glad that helped. I seem to recall somebody on the darkside (Christina?) telling me (or somebody else, memory no good these days) that the number is like an index into some global font list or something.

Fonts in LV do suck quite a bit. I use system style controls exclusively for GUI type FPs. I normally shove these settings into my LabVIEW.ini and app.ini file appFont = "0" 13 dialogFont = "2" 13 systemFont = "1" 13 BDFont = "2" 13 This way the fonts are consistent between OSs that do and do not support high res fonts (i.e. WinXP). I have just tested it out with Win7 set to 150% (I normally use 100%) and it also works fine. These keys also stop the BD getting messed up when a VI is edited on a WinXP and then a Win7 machine (due to font size differences). Note: I have only a vague understanding of what these keys actually do, but they work for me I think these settings force the app to use the fonts specified, and the sizes, so they are not affected by font changes. I have seen similar settings where the actual font is specified (i.e. appFont = "Tahoma" 13 etc) Not sure this is exactly what you are after, but its worth a try.