ThomasGutzler

I understand this can be an issue for users and I have something to add: The select tool on a graph/chart turns into tiny black cross-hairs impossible to locate on black background. Terrible! But as a developer, I wonder how you deal with the fact that you have to have the help window and the probe window on the same screen as your BD for the scroll down menus, context menus and mouse-hover displays (during debugging) to work. It drives me crazy. Although, this might only be an issue when you work with two screens and they run on different zoom levels.

Unfortunately, I'm still stuck in 2016 land. But JKSH's suggestion got me going. Thanks

Hi, I'm receiving a JSON string from a web API, which I'm trying to convert into a cluster (of clusters) but I've run into some problems: 1) Sometimes the order of the elements in the JSON string changes, which causes my conversion to fail. 2) Sometimes the "object" returned via JSON is null, which causes my conversion to fail if I use clusters within clusters. It works with variants in clusters but then I need to convert the all the variants manually Is there any way to improve my code to fix those problems? The attached snippet is a simplified version. In my project, the first JSON string to data is done in a library. The second conversion from "result" variant to data is done in my application. This makes a direct conversion from JSON string more difficult.

That's very much what my plugin is doing as well. Now I just need to figure out how to handle .lvproj

Hi, I'm trying to improve a quickdrop plugin that removes compiled code for my project. I noticed that it doesn't check the box in the project properties but I can't figure out how to do that. I tried reading the "NI.LV.All.SourceOnly" property via the project invoke node "Get Item" but I'm not getting anything back. Is it possible? I can't text edit the project file, because it's currently open.

Could you make a package that opens in VIPM 2016? For complicated reasons, I can't update to 2017

K4zz, I modified the source to be able to run multiple front panels. You can get a copy from github It's in LV2016. Let us know if you have any problems.

Oh wow, this thread is still going. I didn't think anyone would pick this up from where I left it. Thanks hooovahh for jumping in with so many fixes and updates. I haven't had the chance to see what happened to it but I will soon

I built my executable with Debug and "Wait for debugger on launch" enabled. When I run it and attach with LabVIEW, it downloads the vis and then crashes LV. The application remains open and not running. I never get to see the local debug version of the application in LV. If I open the source it runs without problems. The executable runs too, but only if there is LabVIEW installed on the machine - that's why I started debugging it. See crash log below, which I'm not sure how to interpret. The two vis mentioned in there are not broken in the IDE. Any ideas what to do next? #### #Date: Tue, 10 Oct 2017 14:42:22 #OSName: Windows 10 Pro #OSVers: 10.0 #OSBuild: 15063 #AppName: LabVIEW #Version: 16.0f2 32-bit #AppKind: FDS #AppModDate: 2/13/2017 09:03 GMT #LabVIEW Base Address: 0x00400000 InitExecSystem() call to GetCurrProcessNumProcessors() reports: 4 processors InitExecSystem() call to GetNumProcessors() reports: 4 processors InitExecSystem() will use: 4 processors starting LabVIEW Execution System 2 Thread 0 , capacity: 24 at [3590451742.90439940, (14:42:22.904399395 2017:10:10)] starting LabVIEW Execution System 2 Thread 1 , capacity: 24 at [3590451742.90439940, (14:42:22.904399395 2017:10:10)] starting LabVIEW Execution System 2 Thread 2 , capacity: 24 at [3590451742.90439940, (14:42:22.904399395 2017:10:10)] starting LabVIEW Execution System 2 Thread 3 , capacity: 24 at [3590451742.90439940, (14:42:22.904399395 2017:10:10)] starting LabVIEW Execution System 5 Thread 0 , capacity: 24 at [3590451744.55625770, (14:42:24.556257725 2017:10:10)] starting LabVIEW Execution System 5 Thread 1 , capacity: 24 at [3590451744.55625770, (14:42:24.556257725 2017:10:10)] starting LabVIEW Execution System 5 Thread 2 , capacity: 24 at [3590451744.55625770, (14:42:24.556257725 2017:10:10)] starting LabVIEW Execution System 5 Thread 3 , capacity: 24 at [3590451744.55625770, (14:42:24.556257725 2017:10:10)] <DEBUG_OUTPUT> 10/10/2017 14:43:21.731 DWarn 0x5C359BD0: no freeRange list or no elements e:\builds\penguin\labview\branches\2016\dev\source\vi\cloneVI.cpp(412) : DWarn 0x5C359BD0: no freeRange list or no elements minidump id: 5a131b3f-9e0e-4462-a33f-36b0f8b94d96 $Id: //labview/branches/2016/dev/source/vi/cloneVI.cpp#6 $ </DEBUG_OUTPUT> 0x006997BC - LabVIEW <unknown> + 0 0x10014A44 - mgcore_SH_16_0 <unknown> + 0 0x018B1176 - LabVIEW <unknown> + 0 0x018B18E5 - LabVIEW <unknown> + 0 0x01884365 - LabVIEW <unknown> + 0 0x018846A5 - LabVIEW <unknown> + 0 0x018A5903 - LabVIEW <unknown> + 0 0x01836EAA - LabVIEW <unknown> + 0 0x018AF415 - LabVIEW <unknown> + 0 0x009A1299 - LabVIEW <unknown> + 0 0x009B0166 - LabVIEW <unknown> + 0 0x00FE0918 - LabVIEW <unknown> + 0 0x01101929 - LabVIEW <unknown> + 0 0x00FDE022 - LabVIEW <unknown> + 0 0x013D2047 - LabVIEW <unknown> + 0 0x013D2ADB - LabVIEW <unknown> + 0 0x00BA92D1 - LabVIEW <unknown> + 0 0x01EB4817 - LabVIEW <unknown> + 0 0x01F661E5 - LabVIEW <unknown> + 0 0x01EB492C - LabVIEW <unknown> + 0 0x01EE0978 - LabVIEW <unknown> + 0 0x01F657A4 - LabVIEW <unknown> + 0 0x01F4CECB - LabVIEW <unknown> + 0 0x00AE5A05 - LabVIEW <unknown> + 0 0x0145A8F8 - LabVIEW <unknown> + 0 0x0145A91B - LabVIEW <unknown> + 0 0x00BA7981 - LabVIEW <unknown> + 0 0x01600F1B - LabVIEW <unknown> + 0 0x01605C71 - LabVIEW <unknown> + 0 0x01607D18 - LabVIEW <unknown> + 0 0x01EB4817 - LabVIEW <unknown> + 0 0x00CAF9BF - LabVIEW <unknown> + 0 0x00CB2189 - LabVIEW <unknown> + 0 0x00CB254E - LabVIEW <unknown> + 0 0x01EC0329 - LabVIEW <unknown> + 0 0x01F661E5 - LabVIEW <unknown> + 0 *** Dumping Bread Crumb Stack *** *** LabVIEW Base Address: 0x00400000 *** #** prop types: "C:\Users\MFG-LaserCal-1\Desktop\build\LaserCalV2.exe\1abvi3w\user.lib\_LVCommon\LcProcessSpecs_class\utils\LcProcessSpecs_New.vi" #** Loading: "C:\Users\MFG-LaserCal-1\Desktop\build\LaserCalV2.exe\1abvi3w\user.lib\_LVCommon\LcProcessSpecs_class\utils\LcProcessSpecs_New.vi" *** End Dump *** <DEBUG_OUTPUT> 10/10/2017 14:43:26.805 DWarn 0x5C359BD0: no freeRange list or no elements e:\builds\penguin\labview\branches\2016\dev\source\vi\cloneVI.cpp(412) : DWarn 0x5C359BD0: no freeRange list or no elements minidump id: 9e03b61f-a952-492f-84a7-1c132e2646f1 $Id: //labview/branches/2016/dev/source/vi/cloneVI.cpp#6 $ </DEBUG_OUTPUT> 0x006997BC - LabVIEW <unknown> + 0 0x10014A44 - mgcore_SH_16_0 <unknown> + 0 0x018B1176 - LabVIEW <unknown> + 0 0x018B18E5 - LabVIEW <unknown> + 0 0x01839216 - LabVIEW <unknown> + 0 0x0183473D - LabVIEW <unknown> + 0 0x0183A560 - LabVIEW <unknown> + 0 0x01823ED2 - LabVIEW <unknown> + 0 0x018241BD - LabVIEW <unknown> + 0 0x01822664 - LabVIEW <unknown> + 0 0x01821D18 - LabVIEW <unknown> + 0 0x0183A3EB - LabVIEW <unknown> + 0 0x0181AE5D - LabVIEW <unknown> + 0 0x0181EECD - LabVIEW <unknown> + 0 0x0181F8BA - LabVIEW <unknown> + 0 0x010F4FED - LabVIEW <unknown> + 0 0x01100B34 - LabVIEW <unknown> + 0 0x0046C5D2 - LabVIEW <unknown> + 0 0x0046C7EA - LabVIEW <unknown> + 0 0x0046C8F5 - LabVIEW <unknown> + 0 0x00FDF8AD - LabVIEW <unknown> + 0 0x018298E4 - LabVIEW <unknown> + 0 0x018290BC - LabVIEW <unknown> + 0 0x018224B2 - LabVIEW <unknown> + 0 0x00FB1224 - LabVIEW <unknown> + 0 0x00FB1371 - LabVIEW <unknown> + 0 0x01822FFA - LabVIEW <unknown> + 0 0x018216C1 - LabVIEW <unknown> + 0 0x010F3551 - LabVIEW <unknown> + 0 0x01101117 - LabVIEW <unknown> + 0 0x00FDE022 - LabVIEW <unknown> + 0 0x013D2047 - LabVIEW <unknown> + 0 0x013D2ADB - LabVIEW <unknown> + 0 0x00BA92D1 - LabVIEW <unknown> + 0 0x01EB4817 - LabVIEW <unknown> + 0 0x01F661E5 - LabVIEW <unknown> + 0 *** Dumping Bread Crumb Stack *** *** LabVIEW Base Address: 0x00400000 *** #** Loading: "C:\Users\MFG-LaserCal-1\Desktop\build\LaserCalV2.exe\1abvi3w\instr.lib\_BarajaDrivers\Tunable Lasers\VdYenistaT100S_class\Example\Example1.vi\2" #** Loading: "C:\Users\MFG-LaserCal-1\Desktop\build\LaserCalV2.exe\1abvi3w\instr.lib\_BarajaDrivers\Tunable Lasers\VdYenistaT100S_class\Example\Example1.vi" *** End Dump *** <DEBUG_OUTPUT> 10/10/2017 14:43:29.020 Crash 0x00000000: Crash caught by NIER File Unknown(0) : Crash 0x00000000: Crash caught by NIER minidump id: 6b19dd9c-e4a7-433e-b736-08a8fdd75b3e ExceptionCode: 0xC0000005 </DEBUG_OUTPUT> 0x7217146F - nierInterface <unknown> + 0 0x72175D75 - nierInterface <unknown> + 0 0x7217517A - nierInterface <unknown> + 0 0x762FA30D - KERNELBASE <unknown> + 0 0x77CC4AF1 - ntdll <unknown> + 0 0x77C857FD - ntdll <unknown> + 0 0x00000000 - <unknown> <unknown> + 0 *** Dumping Bread Crumb Stack *** *** LabVIEW Base Address: 0x00400000 *** #** prop types: "C:\Users\MFG-LaserCal-1\Desktop\build\LaserCalV2.exe\01_Application\MAIN_LaserCalV2.vi" #** Loading: "C:\Users\MFG-LaserCal-1\Desktop\build\LaserCalV2.exe\01_Application\MAIN_LaserCalV2.vi" *** End Dump ***

Here comes another bump. Getting the 2208 error when running an executable on the same PC where it was built (and runs fine in LV). This is version 2016 32bit. Also getting the error when building on a different PC, same LV version. The project has no libraries, only classes. All dll dependencies are there. I've tried clearing the compiled objects for both user and application builder. And I've installed .net framework 3.5 because that was a thing on the NI forum where a similar error was discussed. Did not help. I tried building a debug version that waits for the debugger and attaching to it with LV but it just crashes LV before the application starts. Also tried hooking DETT into it but it shows nothing - probably because the application never actually starts running but just sits there with a broken run arrow. Ideas?

No, that was 2016 32bit

I spent all day yesterday to port some code across from another project into what I'm currently working on. Closed the project to do a quick fix on something else, opened my project again and found that the vi that has the GUI state machine in it had lost its block diagram, which contained the main part of the changes I had made. And because I hadn't finished the porting I hadn't checked it in. I didn't love LV after that one I wish I knew how I did that.

Wow, really? How disappointing! Where do I have to vote to get that changed?

It's a fresh install and I've activated as "LabVIEW Full Development System". I would have thought that's enough. Can anyone confirm that this is working for LV2017 any bitness

Now that you mention that, I can't find it in the tools menu. There is no "Compare" submenu under tools. I know, I've posted to that thread when it was active, but that was on LV2014 :/

Hi, I'm trying to get LVCompare working (with git) but I'm getting an error when launching lvcompare.exe. To figure out what's going on, I'm manually starting the program from a power shell: PS C:\Program Files\National Instruments\Shared\LabVIEW Compare> .\LVCompare.exe C:\Users\ThomasGutzler\Desktop\vi1.vi C:\Users\ThomasGutzler\Desktop\vi2.vi -lvpath 'C:\Program Files\National Instruments\LabVIEW 2017\LabVIEW.exe' I noticed that lvcompare writes a log file into the temp folder (LVCompare_64_17.0_ThomasGutzler_cur.txt). This is what it says: #### #Date: Wed, 23 Aug 2017 09:16:11 #OSName: Windows 10 Pro #OSVers: 10.0 #OSBuild: 15063 #AppName: LVCompare #Version: 17.0 64-bit #AppKind: AppLib #AppModDate: 3/19/2017 10:14 GMT #LabVIEW Base Address: 0x0000000076C10000 InitExecSystem() call to GetCurrProcessNumProcessors() reports: 4 processors InitExecSystem() call to GetNumProcessors() reports: 4 processors InitExecSystem() will use: 4 processors starting LabVIEW Execution System 2 Thread 0 , capacity: 24 at [3586288571.84286833, (09:16:11.842868329 2017:08:23)] starting LabVIEW Execution System 2 Thread 1 , capacity: 24 at [3586288571.84286833, (09:16:11.842868329 2017:08:23)] starting LabVIEW Execution System 2 Thread 2 , capacity: 24 at [3586288571.84286833, (09:16:11.842868329 2017:08:23)] starting LabVIEW Execution System 2 Thread 3 , capacity: 24 at [3586288571.84286833, (09:16:11.842868329 2017:08:23)] VI_BROKEN (0): [VI "NI_LVConfig.lvlib:Escape String.vi" (0x00000208ff4f5bc0)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlib:Escape String.vi" (0x00000208ff4f5bc0)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_LVConfig.lvlib:Parse Config to Queue.vi" (0x00000208ff526580)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlib:Parse Config to Queue.vi" (0x00000208ff526580)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_LVConfig.lvlib:Config to String.vi" (0x00000208fd5fdb30)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlib:Config to String.vi" (0x00000208fd5fdb30)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_LVConfig.lvlib:String to Config.vi" (0x00000208ff54ca10)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlib:String to Config.vi" (0x00000208ff54ca10)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_LVConfig.lvlib:Close Config Data.vi" (0x00000208fd5ec130)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlib:Close Config Data.vi" (0x00000208fd5ec130)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_FileType.lvlib:Get File Type.vi" (0x00000208ff45bf10)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_FileType.lvlib:Get File Type.vi" (0x00000208ff45bf10)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_LVConfig.lvlib:Typecast Refnum to Queue.vi" (0x00000208fd678fd0)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlib:Typecast Refnum to Queue.vi" (0x00000208fd678fd0)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_LVConfig.lvlib:Save Config File.vi" (0x00000208ff415120)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlib:Save Config File.vi" (0x00000208ff415120)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_LVConfig.lvlib:Add Quotes.vi" (0x00000208ff4f6610)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlib:Add Quotes.vi" (0x00000208ff4f6610)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_LVConfig.lvlib:Parse Key Value Pair.vi" (0x00000208ff5650a0)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlib:Parse Key Value Pair.vi" (0x00000208ff5650a0)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_LVConfig.lvlib:Remove Quotes.vi" (0x00000208ff56b920)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlib:Remove Quotes.vi" (0x00000208ff56b920)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_LVConfig.lvlib:Write Key (String).vi" (0x00000208ff4eb650)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlib:Write Key (String).vi" (0x00000208ff4eb650)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_LVConfig.lvlib:Get File Path.vi" (0x00000208ff43ca10)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlib:Get File Path.vi" (0x00000208ff43ca10)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_LVConfig.lvlib:Add Key.vi" (0x00000208fd6a0310)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlib:Add Key.vi" (0x00000208fd6a0310)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_PackedLibraryUtility.lvlib:Get Exported File List.vi" (0x00000208ff441e10)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_PackedLibraryUtility.lvlib:Get Exported File List.vi" (0x00000208ff441e10)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_LVConfig.lvlib:Get Key.vi" (0x00000208ff4c0900)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlib:Get Key.vi" (0x00000208ff4c0900)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_LVConfig.lvlib:Get Section.vi" (0x00000208ff4d5e00)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlib:Get Section.vi" (0x00000208ff4d5e00)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_LVConfig.lvlib:Load.vi" (0x00000208ff5144b0)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlib:Load.vi" (0x00000208ff5144b0)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_LVConfig.lvlib:New Config to Queue.vi" (0x00000208ff526850)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlib:New Config to Queue.vi" (0x00000208ff526850)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_LVConfig.lvlib:Write Key (Boolean).vi" (0x00000208fd687050)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlib:Write Key (Boolean).vi" (0x00000208fd687050)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_LVConfig.lvlib:Typecast Queue to Refnum.vi" (0x00000208ff4ce860)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlib:Typecast Queue to Refnum.vi" (0x00000208ff4ce860)] this->flags=33563136, compilerError=6 VI_BROKEN (0): [VI "NI_LVConfig.lvlib:Open Config Data.vi" (0x00000208ff50cd90)] VirtualInstrument::SetOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlib:Open Config Data.vi" (0x00000208ff50cd90)] this->flags=33563136, compilerError=6 stopping LabVIEW Execution System 2 Thread 0 , capacity: 24 at [3586288577.51620388, (09:16:17.516203881 2017:08:23)] stopping LabVIEW Execution System 2 Thread 1 , capacity: 24 at [3586288577.51620388, (09:16:17.516203881 2017:08:23)] stopping LabVIEW Execution System 2 Thread 2 , capacity: 24 at [3586288577.51620388, (09:16:17.516203881 2017:08:23)] stopping LabVIEW Execution System 2 Thread 3 , capacity: 24 at [3586288577.51620388, (09:16:17.516203881 2017:08:23)] Possible path leak, unable to purge elements of base #0 Something is wrong with NI_LVConfig.lvlib? I tried opening that library and didn't get any errors. I also have LV2017 32bit and LV2016 32bit installed and tried launching lvcompare like this: PS C:\Program Files (x86)\National Instruments\Shared\LabVIEW Compare> .\LVCompare.exe C:\Users\ThomasGutzler\Desktop\vi1.vi C:\Users\ThomasGutzler\Desktop\vi2.vi -lvpath 'C:\Program Files (x86)\National Instruments\LabVIEW 2017\LabVIEW.exe' and this: PS C:\Program Files (x86)\National Instruments\Shared\LabVIEW Compare> .\LVCompare.exe C:\Users\ThomasGutzler\Desktop\vi1.vi C:\Users\ThomasGutzler\Desktop\vi2.vi -lvpath 'C:\Program Files (x86)\National Instruments\LabVIEW 2016\LabVIEW.exe' with very similar results in LVCompare_32_17.0_ThomasGutzler_cur.txt What am I doing wrong? LVCompare_32_17.0_ThomasGutzler_cur.txt LVCompare_64_17.0_ThomasGutzler_cur.txt

Here's something that doesn't work. Maybe someone can spot the bug Watch out for the OpenG trim whitespace! crc16.vi

Not really. What's this "item from the display"? I don't understand if you're just dropping a single or multiple files or multiple files individually. And what those functions "it" can call? Are you writing to the text file that you dropped onto the UI? Mike's VI only handles text files. If you want to open images, you have to modify the "OpenFile" case.

That seems like a great util to start a code clean-up with. I've done this so many times manually to replace those vis with my own SetError.vi that takes an error type-def instead of the numeric. Would you share it around when you've got it working? Productivity++ Edit: Also, it would be nice to be able to reduce the list of inspected files a root folder + subfolders (so we can ignore stuff that comes out of external libraries or the LabVIEW folder)

I'm not sure if the drag&drop operation is the problem here. To me it seems more like the presentation of the files could be problematic. You are trying to do this for multiple files, right? LabVIEW isn't the language of choice when trying to make pretty UI stuff. OTOH I haven't used movie maker for a long time so I can't quite remember how it represents pictures - I'm imagining tiles (There's a demo somewhere that shows how to implement windows 8/10 style UI tiles on a FP but I can't find it now). But as a newcomer to LV, you'd be entering the world of pain.

I won't get my hands on 2015 for a long time unfortunately But good to know they're working on it

I really liked the idea of the bookmark manager, but I'm a little disappointed by how slow it is. My "small" project has 2600 files (in memory) and the bookmark manager takes around 40s to open. Plus, every time I modify a bookmark it takes another 40s to update. This is often a serious interruption in workflow. I click on a TODO bookmark, do the work, remove the bookmark, save the VI and then I'm sitting there waiting for the bookmarks to update before I can go to the next item. I just can't convince myself to go to the next bookmark BEFORE saving the file I'm currently working on. How do use it?

You should probably build your code into an executable to avoid the dev env overhead before doing the benchmarking

TDM? Is that a copy&paste-o? It points to the right target.

I think you'll find that "affordable industry PC" is a bit of an oxymoron