karolek Posted April 19, 2015 Report Share Posted April 19, 2015 (edited) Hi guys, I've got some problem with my project. It's rather small one (3 classes, about 200 vi) I've started to work on one of the classes a 2 months and now, to open ctl file for that class, I need about 3 minutes (after double click on class.ctl I'm seeing white window that populates with controls after 3 minutes). The other classes opens with no delay at all. I was tagging this project by saving it to my drive every week. Now I've spotted that about a month ago, I've changed this class a bit, adding couple extra clusters and from that on, I'm seeing this massive hang of LabVIEW before showing me class private data. After deleting this cluster (up to the point when I've deleted every data from this class) and saving it, time to open didn't change. How to spot which vi is causing this opening time? How is it working? If I would have to build this class from the month ago base, how should I do it so that LabVIEW will not complain about the today's-class that he is using? Any response and ideas appreciated Mass compile didn't help Edited April 20, 2015 by karolek Quote Link to comment
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.