v1.0.0-build598

[svelderrainruiz]

The purpose of this discussion is for users to post the problems they are having with the release, with the intention of referencing those comments on actual GitHub issues later on if they turn on to be actual bugs.

For visibility, these are the features included in the release:

#22 Handle underscores in filename when using "Set Icon to VI Name" by @JayKayAce in #43
#112 Show the Layers tab permanently and remove the show layers menu option by @crossrulz #127
#114 "Unsaved changes" dialogue when cancelling with unsaved changes by @crossrulz in #262
#162 Enable VI Package to be installed without running VI Package Manager in Admin mode for LabVIEW>2022 @HasbunWoodEngineering in #272
#209 Ability to click the cancel button by pressing the esc key by @crossrulz in #225 #261

[FireFist-Redhawk]

I've tried a bunch of different things to fix my setup after uninstalling build598. I will be doing a full purge of all LabVIEW products soon, but at the moment, I am wondering what are these files used for?

After uninstalling IE from all LV versions, my most recent troubleshooting effort has been deleting the C:\Users\Public\Documents\National Instruments\LabVIEW Icon Editor folder and all its contents. After doing that, if I try to install build625, I get this error, as the installer does not put those files in the folder:

However, if I then try to install build 590, that error does not occur because those files are put there by the installer.

I assumed those were packed libraries with their extensions changed, so I then changed the extension to .lvlibp and went into Properties > Details, and the version number was 0.2.0.590. I changed the extension back.

I upgraded to build 625 after that, and checked the versions again in the same manner, and they were still 0.2.0.590. Also, I checked the version of the packed library located at C:\Users\Public\NI\LVAddons\niiconeditor64\1\resource\plugins, and it too was still at build 590. This has all been using LabVIEW 2024 64b.

I'll do the purge soon, but I wanted to share what I had found out tonight prior to doing that.

[crossrulz]

A full purge probably isn't necessary. A repair has been enough to fix these thing for me.

@svelderrainruiz would be the one who most understands the install/uninstall process.

[FireFist-Redhawk]

Proceeding as directed by @svelderrainruiz (https://discord.com/channels/1015999107921354932/1314197455298105355/1390405010260754523):

In 2024 64b, I have build 625 installed. It is seemingly not installed correctly, as a fix that should be implemented is not there for me. It is seemingly on build 590 still. The folder C:\Program Files\NI\LVAddons\niiconeditor64 does not currently exist for me. The folder C:\Users\Public\NI\LVAddons\niiconeditor64 does exist.

1. Ran VIPM as admin.
2. Uninstalled build 625.
3. Checked for existence of C:\Users\Public\NI\LVAddons\niiconeditor64. It no longer existed, but the containing folder (LVAddons) still did.
4. Deleted C:\Users\Public\Documents\National Instruments\LabVIEW Icon Editor.
5. Attempted a reinstall of build 625. NI Icon Editor (System) v1.4.1.625 installed successfully, but NI Icon Editor v1.4.1.625 installation failed with Error Code 7, as before.
6. Attempted an install of build 590. v0.2.0.590 installed successfully, and (System) v0.2.0.590 downgraded successfully.
7. Checked for the existence of C:\Program Files\NI\LVAddons\niiconeditor64. It did exist and contained a packed library with the same version several hierarchy levels down.
8. Checked for the existence of C:\Users\Public\NI\LVAddons\niiconeditor64. It did exist but did not contain a packed library within the hierarchy.
9. Upgraded to build 625. Both packages upgraded successfully.
10. Checked for the existence of C:\Program Files\NI\LVAddons\niiconeditor64. It no longer existed.
11. Checked for the existence of C:\Users\Public\NI\LVAddons\niiconeditor64. It did exist and contained a packed library in the hierarchy, but the library was version 0.2.0.590.

At this point, I was back where I was at the start of these steps.

[FireFist-Redhawk]

I came up with a bit of a hacky workaround to seemingly update myself to the latest version of IE, to where the clipboard bug no longer occurs:

1. Navigated to C:\Users\Public\Documents\National Instruments\LabVIEW Icon Editor\install\plugins and copied lv_icon_x64.lvlibp.
2. Navigated to C:\Users\Public\NI\LVAddons\niiconeditor64\1\resource\plugins, which contains lv_icon.lvlibp.
3. Pasted lv_icon_x64.lvlibp into that location.
4. Renamed lv_icon.lvlibp to some other name.
5. Renamed lv_icon_x64.lvlibp to lv_icon.lvlibp.

[FireFist-Redhawk]

I figured I would see if I could get the latest version of IE on 2023 32b (the version of LV that I currently use), and it seems as though the bitness changes things. Build 590 works as expected, and with that version installed, the folder C:\Program Files\NI\LVAddons\niiconeditor32 does exist. With build 625 installed, that folder no longer exists. So far, this has been the same behavior as before. However, when I open the IE with build 625 installed, I get the very old IE interface from many years ago.

If I copy C:\Program Files\NI\LVAddons\niiconeditor32 before it gets deleted by the upgrade, upgrade versions, and then paste it back into place, the current IE interface appears again. It seems like on build 625, 64b looks in one folder for the IE, and 32b looks in another folder.

So, in summary, the way I got a working build 625 in LV 2023 32b was the following:

1. With build 590 installed, made a copy of C:\Program Files\NI\LVAddons\niiconeditor32.
2. Upgraded to build 625.
3. Pasted the copied folder and contents into place.
4. Navigated to C:\Users\Public\Documents\National Instruments\LabVIEW Icon Editor\install\plugins and copied lv_icon_x86.lvlibp.
5. Navigated to C:\Program Files\NI\LVAddons\niiconeditor32\1\resource\plugins, which contains lv_icon.lvlibp.
6. Pasted lv_icon_x86.lvlibp into that location.
7. Renamed lv_icon.lvlibp to some other name.
8. Renamed lv_icon_x86.lvlibp to lv_icon.lvlibp.

[FireFist-Redhawk]

@svelderrainruiz @crossrulz I may have figured out what was going on with my setup. I saw #311, and maybe this was noticed already and that is the start of the fix for it... From what I can tell, the LVAddons.AdditionalLocations INI key wasn't released until 2024Q1. That would explain why I had to move the file the way I did when working in 2023.