Palette editing broken in 2023.1

[negentropicdev]

Short Description of the Bug (in one or two sentences)

Please provide a clear and concise description of the bug.

VIPM hangs anytime I try and edit palettes for packages.

`=========== START of VIPM 2023.1 (build 2498) Error Message ===========
An internal VIPM 2023.1 (build 2498) Error has occured on: Monday April 10, 2023 at 10:19:17 AM

= Automated Message Start =
Error 6 occurred at Delete in Floating Palette Preview - UI - .vi:4010002->Floating Palette Preview

• UI - .vi.ACBRProxyCaller.E940004E
  Possible reason(s):
  LabVIEW: (Hex 0x6) Generic file I/O error.
  C:\dev\lv20CE\lv-http-util\OAuth2
  = Automated Message End =

= Error Handler Call Chain Start =
Floating Palette Preview - UI - .vi.ACBRProxyCaller.E940004E->
Floating Palette Preview - UI - .vi:4010002
= Error Handler Call Chain End =
=========== END of VIPM 2023.1 (build 2498) Error Message ===========`

Version Information

VIPM Version and Build:

You can get this information on the Help >> About window or Splash Screen
2023.1 (build 2498)

Operating System Version:

For example: Windows 10, Windows 11, Ubuntu 22.04.1, MacOS 10.14.6 (Mojave)
Windows 11

LabVIEW Version:

For example LV2019, LV2021 SP1, LV2022 Q3
LV 2020

LabVIEW Bitness:

32-bit or 64-bit LabVIEW?
32

Virtualization or Processor Version Information

Are you running in a Virtual Machine?
Do you have a Mac with an Apple M1 or M2 (ARM) Processor?
Not in a VM

Steps To Reproduce

What are the steps to reproduce the behavior? (you can replace the text below with your exact steps)
For example:

1. Go to '...' [screen/page/etc]
2. Click on '....' [button/menu-item/etc.]
3. Scroll down to '....' [section/list]
   Open package builder, attempt to add a subpalette to the function palette. Accepts the name and then hangs.

Expected behavior

What did you expected to happen (if the bug didn't exist)?
It doesn't hang and lets me edit palettes.

Actual Behavior

What to you observe that happened (instead of what you expected)?
It hangs

Screenshots

If applicable, please add screenshots to help explain your problem.

https://www.youtube.com/watch?v=YICYQMkvYwo

Anything else you'd like us to know?

Please add anything else you'd like us to know

[jimkring]

Thanks for posting this Derrick! We've reproduced and isolated the issue -- it was related to the upgrade to 64-bit LabVIEW and some issues with WinAPI calls. We should have a fix available for testing soon...

[jimkring]

Hi @negentropicdev. This should be fixed in 2023 Q3. You can get the release candidate here:

--> VIPM 2023 Q3 for Windows Release Candidate Available