10-10-2024 03:16 PM
@avogadro5 wrote:
Will the fix for this arrive via a patch for 2024 Q3 or in 2025 Q1? Upgrading to a new version year is an expensive effort for developers so people shouldn't be upgrading to a version with a major bug that won't be fixed.
I did find out there was a patch released recently (today?). I will install it in the morning and see if this fix is in there. The bug fix list hasn't been updated yet (as of an hour ago).
10-10-2024 05:51 PM
I hate to be the bearer of bad news, but the fix did make it into the 2024 Q3 patch that has just released.
According to the 'paperwork' the fix is scheduled to be included in the LabVIEW 2025 Q1 release, which will be shipped on...
David.
10-11-2024 07:27 AM
Let me fix your post for (changes in red)...
AustinMan@NI wrote:
I hate to be the bearer of bad news, but the fix did not make it into the 2024 Q3 patch that has just released.
According to the 'paperwork' the fix is scheduled to be included in the LabVIEW 2025 Q1 release, which
willmay be shippedon...
David.
I'm just having fun with your post. Thanks for the feedback.
10-14-2024 03:27 AM - edited 10-14-2024 03:36 AM
Related to what aeastet and crossrulz reported above, I can confirm that on my machine:
OS: Windows 11 64-bit
LabVIEW version: LabVIEW 2024 Q3 64-bit.
10-14-2024 03:20 PM
@crossrulz wrote:
Let me fix your post for (changes in red)...
AustinMan@NI wrote:
I hate to be the bearer of bad news, but the fix did not make it into the 2024 Q3 patch that has just released.
According to the 'paperwork' the fix is scheduled to be included in the LabVIEW 2025 Q1 release, which
willmay be shippedon...
David.
I'm just having fun with your post. Thanks for the feedback.
In my testing it is in fact fixed in patch 2... Are people still replicating it on the latest patch? I'm on Windows 10 w/ LV 32 bit.
10-14-2024 03:22 PM
I am still seeing it. I am running Windows 11 and 64 bit LabVIEW.
10-14-2024 03:32 PM
Will be a tough one - New bugs from 25 versus this one fixed
10-15-2024 02:53 AM
To confirm, the exact LabVIEW version on my machine is 24.3.1f1 64-bit. I have not tried the f2 patch yet.
10-17-2024 06:10 AM
I finally got around to testing this with the patch 2 installed and I am no longer getting a crash. The exact bug in the fixed list is #2826505, LabVIEW Crashes When Using Custom VI Menus and Actor Framework.
LabVIEW 2024Q3 f2, 64-bit
Windows 10
10-18-2024 04:19 AM
I too am happy to report that the Edit >> Import Icon from Owning Library... bug does not occur anymore after upgrading to the f2 patch.
Additionally, there was a second bug which was fixed on my machine. Since a few weeks ago the custom right-click menu plugins (a.k.a. shortcut menu plugins) that were installed on my machine stopped working. The menu items would appear in the right-click menus, but when clicking them nothing would happen. The right-click menu plugins were working correctly when I first installed the f1 patch, and later they stopped working. I don't know what triggered this bug to start occurring - perhaps I had installed too many right-click menu plugins, or I had installed one that caused this behaviour to start occurring. Fortunately this bug is also fixed now after the upgrade to f2 and the right-click menu plugins are working again.