LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Rearrange cases (edit time plugin) dialog not showing

Something seems to have gotten corrupted in my LabVIEW 2022 installation and if I select Rearrange Cases on a case structure no dialog will show.

 

Now, I suspected that this could be a corrupt edit time plugin so I checked the ReArrange Cases.llb file in C:\Program Files (x86)\National Instruments\LabVIEW 2022\resource\plugins\PopupMenus\edit time panel and diagram and it seems to be runnable  if opened directly (it is the original plugin too, not some replacement) I also tried to replace it and/or all the plugins in that directory, but to no avail.

 

The issue is obviously connected to the plugin though because if it is removed I will get the old legacy dialog just fine...Any idea on how to fix this other than to run a full fix/reinstall of LabVIEW on the machine?

0 Kudos
Message 1 of 7
(189 Views)

If memory serves those VI's must have Debugging disabled (all plugins must). Check that.

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 2 of 7
(172 Views)

Do all the other right-click plugins work ok?

 

Can you mass compile your plugins folder?

 

Maybe copy over the plugin LLB from another LabVIEW install and mass compile?

 

Can you rename your LabVIEW INI file to LabVIEW.bak to make sure there aren't any errant INI tokens causing the issue?

I can't think of anything else to try other than a repair of the install.

Message 3 of 7
(155 Views)

It ended up seemingly fixing itself...

 

I had moved the original one out and put in a copy from someone elses machine without it working..

 

Then I replaced the whole edit time folder of plugins with a copy from someone elses machine...Nothing worked. Then I copied back my original edit time folder and voila, now it works.

 

I never tried to recompile or clear the object cache but perhaps that was triggered and fixed it by the actions I did take.

Message 4 of 7
(117 Views)

@Mads wrote:

I never tried to recompile or clear the object cache but perhaps that was triggered and fixed it by the actions I did take.


That sounds reasonable.

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 5 of 7
(113 Views)

@Mads wrote:

It ended up seemingly fixing itself...

 

I had moved the original one out and put in a copy from someone elses machine without it working..

 

Then I replaced the whole edit time folder of plugins with a copy from someone elses machine...Nothing worked. Then I copied back my original edit time folder and voila, now it works.

 

I never tried to recompile or clear the object cache but perhaps that was triggered and fixed it by the actions I did take.


I would "Guess" that "Someone Else(tm)" accidentally changed the VI Property FP.Behavior.   That sometimes happens when you kill non-running Modal vis.  Using the dangerous Abort.vi or Revolk All Modals.vi when you accidentally hung LabVIEW with an open idle Modal front panel. 

 

Better: revise the dialog to set FP.Behavior at runtime (the Property is runtime writeable.)  

 

NI needs to refactor dialog vis to use that better practice ( and stop polling too!)


"Should be" isn't "Is" -Jay
0 Kudos
Message 6 of 7
(99 Views)

@Darren wrote:

Do all the other right-click plugins work ok?

 

Can you mass compile your plugins folder?

 

Maybe copy over the plugin LLB from another LabVIEW install and mass compile?

 

Can you rename your LabVIEW INI file to LabVIEW.bak to make sure there aren't any errant INI tokens causing the issue?

I can't think of anything else to try other than a repair of the install.


@dnatt. There really should be a CAR on the BUG "LabVIEW IDE hangs if any idle Dialog.vis have FP open when any vi is run."  It's solvable with runtime writable properties FP.BEHAVIOR and FP.CLOSABLE. Make Dialogs Modal only while running!!  I would argue that we NEVER DESIRE that the IDE should hang simply because an idle VI has FP.BEHAVIOR set to Modal.  LabVIEW itself is smart enough to apply those properties ONLY when the VI.STATE is not "Idle" (or "non-runnable"/broken)


"Should be" isn't "Is" -Jay
0 Kudos
Message 7 of 7
(94 Views)