Jump to content

Search the Community

Showing results for tags 'class private data'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Software & Hardware Discussions
    • LabVIEW General
    • LabVIEW (By Category)
    • Hardware
  • Resources
    • LabVIEW Getting Started
    • OpenG
    • Code Repository (Certified)
    • LAVA Code on LabVIEW Tools Network
    • Code In-Development
  • Community
    • LAVA Lounge
    • LabVIEW Feedback for NI
    • LabVIEW Ecosystem
  • LAVA Site Related
    • Site Feedback & Support
    • Wiki Help

Categories

  • *Uncertified*
  • LabVIEW Tools Network Certified
  • LabVIEW API
    • VI Scripting
    • JKI Right-Click Framework Plugins
    • Quick Drop Plugins
    • XNodes
  • General
  • User Interface
    • X-Controls
  • LabVIEW IDE
    • Custom Probes
  • LabVIEW OOP
  • Database & File IO
  • Machine Vision & Imaging
  • Remote Control, Monitoring and the Internet
  • Hardware

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Personal Website


Company Website


Twitter Name


LinkedIn Profile


Facebook Page


Location


Interests

Found 1 result

  1. 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
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.