New in CVI 2019

[gdargaud]

Hello all,

I was going through the readme of the new version to see what I've missed (http://www.ni.com/pdf/manuals/374674e.htm) and there are several things I can't figure out:

• Customizable code snippets - I guess that relates to the [Insert construct], but how to you add new constructs ?
• Ability to quickly identify code changes with file modification indicators. How ? Is that related to the useless Version Control, or is that the [Edit][Diff] menu (which is always greyed out for me)
• Edit multiple lines at the same time - How ?
• Remove trailing spaces - How ?
• Word wrap - How ?
• GetInfoByZip - What is that ? Can't find a new file or function by that name

[IEE_newsoft]

This is not really a reply, it's rather another question that came up for me as I'm on the same page:

I upgraded from CVI9.0.1 to CVI2019 yesterday. While I highly appreciate some of the new editor features, I miss a very useful feature:

In the workspace explorer I don't see anymore if a file needs to be compiled. In CVI9.0.1, such a file was flagged in red color. Especially in case of dependencies between DLLs, this was a very essential feature. Now I have check manually if it's necessary to recompile a depending DLL. Does someone know how to re-enable this visual feature?

I also recognized that the keyboard shortcuts Alt+B ->F ->D(debug) or ->R (Release) to quickly toggle between release and debug configuration do no longer work. Alt+B ->F still works, but D/R doesn't as there is no underlined character.

Regards

[RobertoBozzolo]

---

@IEE_newsoft  ha scritto:

I also recognized that the keyboard shortcuts Alt+B ->F ->D(debug) or ->R (Release) to quickly toggle between release and debug configuration do no longer work. Alt+B ->F still works, but D/R doesn't as there is no underlined character.

Regards

---

With reference to this last question, you can add some configurations more (Build >> Configuration >> Manage Configurations...) simply copying the existing ones and adding a proper __Name: your keyboard shortcuts will then be active again 😊

Note that the active configuration is reported in the lower right corner of the workspace status bar (unfortunately this is not an active field as it is, for example, INS/OVR field next to it)

[IEE_newsoft]

Hi Roberto,

thanx for posting this workaround, it works!

Highly appreciated 🙂

Any idea about my central question?

Regards

[RobertoBozzolo]

None that I can easily think of

[IEE_newsoft]

I think I have to report this on the support page.

Nevertheless, thanx again for your help!

[Wolfgang]

With regard to your central question: files that have been changed are marked by an asterisk after the file name

[IEE_newsoft]

If a source file has been modified, of course. But imagine you change a header file. Does the asterisk then also appear on the source files that included this header? A clear no!

Furthermore imagine this header being also used by foreign DLL modules....

I have a workspace that contains modules for an executable surrounded by 50 DLLs that also interact. It's a very big test bench tool that controls lots of devices. This visual flag helps a lot when maintaining the code when adding/changing features.

I did a support request on this topic: https://sine.ni.com/srm/app/details?id=7796722

[Wolfgang]

This support request has been issued seven years ago - NI replied that this idea is unlikely to be implemented, see here

[IEE_newsoft]

..so you complained exactly the same thing...lol

Based on what NI is telling there, I still cannot see any benefits from having it removed. It makes absolutely no sense to modify code why the compiler is running the build process. Furthermore if a build process would take too long for a user sitting in front of the PC waiting for completion, I tend to say that such a project is badly organized, things should rather be grouped into DLLs. As long as you don't change export headers you don't have to recompile the whole project in such a modular environment.

Regards

Manfred