Labview 2017 - Icon editor very slow.

[Penzium]

Hi all,

I have converted a project from Labview 2019 to Labview 2017 using "Save for previous version" menu. The project seems ok but when I use the icon editor it is very slow, 20-30 seconds in order to open and is slow also during the usage, for example typing text is very slow.

I have recreated the project from scratch but the problem persist and it is present only in this project because other projects developed natively in Labview 2017 doesn'have this problem. I think this behavior could be do to the conversion.

Sameone have experienced similar problems after a labview conversion?

Thanks.

Luca

[wiebe@CARYA]

---

@Penzium wrote:

Sameone have experienced similar problems after a labview conversion?

---

No, like most of us I prefer to go up in version. 😁

There is a change a mass compile fixes things.

You can try clearing your compile cache, especially if the project was opened in LV17 before converting to LV19 (e.g. the save to previous VIs are in LV17's cache).

If you save a single VI back to 17, does it have the problem?

Are your VIs in libraries or classes? It could be the lib\class icon that's used in the VIs. Editing it might make a difference.

[Penzium]

Thanks for the reply.

I did a clear cache and a mass compile but the problem persists. I have two libraries I have open and edited all the VIs of the libraries but with this VIs the Icon editor is fast.

The problem seems to be related with only some VI, in example main.vi and other more complex VIs.

I think the best solution should be not doing conversion back to older versions.

Luca

[wiebe@CARYA]

---

@Penzium wrote:

I have two libraries I have open and edited all the VIs of the libraries but with this VIs the Icon editor is fast.

---

But did you edit the library icon?

The library icon is in all VI icons as well (at least optionally).

Probably another red haring, but worth a try.

If the problematic VIs are not in the libraries, never mind...

---

@Penzium wrote:

I think the best solution should be not doing conversion back to older versions.

---

If you have a choice, why would you?

Version conversion is definitely not something most of us take lightly. In general it works OK (esp. going up), but it's something most of us avoid if possible.